CVE-2026-126287nocodb race condition
CVE-2026-126287 is a race condition in nocodb, rated medium (6.0 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Two operations race on shared state, and an attacker who wins the race bypasses a check or corrupts data.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker win a timing window to bypass a check or corrupt shared state.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.22% chance of exploitation activity in the next 30 days, higher than 12% of scored CVEs.
What to do
- Upgrade nocodb to 2026.06.2 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Request handlers and jobs that share state. The flaw sits between concurrent requests or processes.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between concurrent requests or processes. An attacker who crosses it can win a timing window to bypass a check or corrupt shared state.
Questions to answer about your own systems
- Where does nocodb run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.