Read the docs

Refresh token reuse via race condition in NocoDB

Priority LOW 39CWE-362Published · Updated

Key facts

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

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

Summary

NocoDB before 2026.08.0 has a race condition in refresh-token rotation, so a token can be reused. The UserRefreshToken.ts code never checks the affected-row count, which is a concurrent access flaw (CWE-362). An attacker who holds a captured refresh token can present it at the same time as the legitimate user to obtain a valid authenticated session. No reuse event is recorded.

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

Description from the CNA

NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid authenticated session, and no reuse event is recorded.

Why it matters now

EPSS 0.00234 14th percentileScored 2026-11-16
Fix Fixed nocodb (nocodb): 2026.08.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
nocodbnocodbbefore 2026.08.02026.08.0Patch availableCNA
  • nocodb Vendornocodb Affected before 2026.08.0 Fixed in 2026.08.0 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.08.0 or later, which fixes the flaw.

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

  • Fix · CNA nocodb (nocodb) Fixed in 2026.08.0

Fixed in the same release

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

  • Release ·

    nocodb 2026.08.0

    8 records Highest priority Priority MEDIUM 3 MEDIUM, 5 LOW

    Other records, highest priority first

    • TI-2026-91224 Reflected cross-site scripting in NocoDB via ncRedirectUrlPriority MEDIUM 45
    • TI-2026-91212 Stored cross-site scripting in NocoDB table deletion dialogPriority MEDIUM 42
    • TI-2026-91221 Incorrect authorization in NocoDB lets base-scoped API tokens access all basesPriority MEDIUM 40

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-126280
  2. 2026-11-13 Alias added: GHSA-qmfq-9h33-q6xx

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