nocodb · nocodb · CWE-362 · published 2026-11-13
CVE-2026-126280NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation
Routine No exploitation evidence; EPSS 0.2%.
CVE-2026-126280 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This nocodb vulnerability: CVSS 9.1 (v4.0), a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.2% (15th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.1 (v4.0)CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization
Affected versions (from the CVE record)#
- nocodb nocodb
0to before2026.08.0(affected)2026.08.0(unaffected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.