NocoDB before 2026.06.2 OAuth Refresh Token Rotation Race Condition
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.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. | |
| Title | NocoDB before 2026.06.2 OAuth Refresh Token Rotation Race Condition | |
| 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.