CVE-2026-126287
Received Received - Intake

Race Condition in NocoDB OAuth Token Rotation

Publication date: 2026-11-13

Last updated on: 2026-11-13

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-13
Last Modified
2026-11-13
Generated
2026-11-13
AI Q&A
2026-11-13
EPSS Evaluated
N/A
NVD
CVE-2026-126287
EUVD
EUVD-2026-125234

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nocodb nocodb to 2026.06.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-126287 is a race condition vulnerability in NocoDB versions before 2026.06.2. It affects the OAuth refresh token rotation process in oauth-token.service.ts. Due to improper synchronization, attackers can capture a valid refresh token and race the legitimate client to reuse it before the system detects the duplicate. If successful, the attacker obtains their own access and refresh tokens, maintaining scoped access without triggering reuse detection.

Detection Guidance

Detecting this vulnerability requires monitoring OAuth token rotation logs for concurrent reuse of refresh tokens. Check NocoDB server logs for multiple successful token refreshes using the same refresh token within a short timeframe. Look for entries in oauth-token.service.ts logs indicating non-atomic token rotation. Review network traffic for unusual OAuth token exchange patterns between clients and the NocoDB server.

Impact Analysis

If exploited, this vulnerability allows attackers to gain unauthorized access to your NocoDB account or data. They can maintain this access by obtaining new tokens without the legitimate user detecting the breach. Attackers only need a captured refresh token to attempt exploitation.

Compliance Impact

This vulnerability could lead to unauthorized data access, violating confidentiality requirements in GDPR and HIPAA. It may result in data breaches, non-compliance with access control policies, and potential legal consequences for organizations failing to protect sensitive information.

Mitigation Strategies

Upgrade NocoDB to version 2026.06.2 or later immediately to patch the race condition. Implement rate limiting on OAuth token refresh endpoints to prevent concurrent requests. Monitor and revoke all active refresh tokens issued before the upgrade. Review OAuth client configurations and audit recent token usage for signs of exploitation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-126287. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...