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.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 13 Nov 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation | |
| First Time appeared |
Nocodb
Nocodb nocodb |
|
| Weaknesses | CWE-362 | |
| CPEs | cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Nocodb
Nocodb nocodb |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-13T09:36:39.321Z
Reserved: 2026-11-10T20:14:15.972Z
Link: CVE-2026-126280
No data.
Status : Received
Published: 2026-11-13T10:17:31.360
Modified: 2026-11-13T10:17:31.360
Link: CVE-2026-126280
No data.
OpenCVE Enrichment
No data.
Weaknesses