NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| nocodb | nocodb | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| 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
|
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
No data.
No data.
No data.
No data.