Read the docs

Race condition in NocoDB OAuth refresh token rotation

Priority LOW 26CWE-362Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

NocoDB before 2026.06.2 contains a race condition in oauth-token.service.ts (CWE-362) where non-atomic refresh token rotation lets concurrent requests reuse a token. An attacker holding a captured refresh token can race the legitimate client to obtain their own access and refresh tokens, keeping scoped access without triggering reuse detection.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

NocoDB before 2026.06.2 contains a race condition vulnerability in oauth-token.service.ts that allows attackers to reuse a refresh token by presenting it concurrently during non-atomic rotation. Attackers holding a captured refresh token can race the legitimate client to obtain their own access and refresh tokens, retaining scoped access without triggering reuse detection.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00233 14th percentileScored 2026-11-16
Fix Fixed nocodb (nocodb): 2026.06.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
nocodbnocodbbefore 2026.06.22026.06.2Patch availableCNA
  • nocodb Vendornocodb Affected before 2026.06.2 Fixed in 2026.06.2 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*——nocodb
  • cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:* Versions — — ·nocodb

Remediation

Upgrade NocoDB to version 2026.06.2 or later, which fixes the issue. The sources list no advisory identifier for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

  • Fix · CNA nocodb (nocodb) Fixed in 2026.06.2

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    nocodb 2026.06.2

    5 records Highest priority Priority MEDIUM 1 MEDIUM, 4 LOW

    Other records, highest priority first

    • TI-2026-91229 SQL injection in NocoDB via user email in base user queryPriority MEDIUM 40
    • TI-2026-91231 Attachment size limit bypass in NocoDB via upload by URLPriority LOW 32
    • TI-2026-91217 Stored cross-site scripting in NocoDB AI field prompt tooltipPriority LOW 31

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-126287
  2. 2026-11-13 Alias added: GHSA-2g7w-6p94-6352
  3. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2023-17918 NocoDB through 0.106.0 (or 0.109.1) has a path traversal vulnerability that allows an… CVSS 3.1HIGH 7.5
  • TI-2023-27191 NocoDB Vulnerable to Stored Cross-Site Scripting in Formula.vue CVSS 3.1HIGH 7.6
  • TI-2026-19968 NocoDB has Blind SSRF via Unvalidated HEAD Request in uploadViaURL Functionality CVSS 3.1MEDIUM 6.4
  • TI-2023-04694 Improper Input Validation in nocodb/nocodb CVSS 3.1MEDIUM 6.5
  • TI-2026-34945 NocoDB: Postgres SQL Injection in Formula `ARRAYSORT` CVSS 3.1MEDIUM 6.0
  • TI-2025-20338 NocoDB Vulnerable to Reflected Cross-Site Scripting on Reset Password Page CVSS 3.1MEDIUM 6.1
See all 87 →

Sources