CVE
NocoDB race condition in password reset enables account lockout
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.08.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.08.1.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
NocoDB before 2026.08.1 contains a race condition vulnerability in users.service.ts that allows holders of a valid reset token to perform multiple password changes by sending concurrent reset requests. Attackers can exploit the window created by slow bcrypt hashing before the token is cleared to overwrite the owner's new password and lock them out.
Who should check
Teams running NocoDB before 2026.08.1, including self-hosted instances where password reset tokens are in use
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2026.08.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126278 (NocoDB before 2026.08.1 Password Reset Token Race Condition), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126278 (entry last updated 2026-11-13):
Affected:
- nocodb nocodb: fixed in 2026.08.1
Fixed versions: 2026.08.1.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.08.1 (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-password-reset-token-race-condition)
- Attacker sends concurrent password reset requests using the same reset token (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-password-reset-token-race-condition)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126278 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126278 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nocodb/nocodb/security/advisories/GHSA-7mf9-q77p-r4r3
- https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-password-reset-token-race-condition
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126278
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126278"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.08.1
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126278
Is CVE-2026-126278 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A race condition in NocoDB's password reset lets someone holding a valid reset token send concurrent reset requests, making multiple password changes so the owner's new password can be overwritten and the owner locked out of the account.Source: vulncheck.com
Which versions are affected by CVE-2026-126278?
nocodb: before 2026.08.1.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.08.1 are affected. To check a deployment, look at the NocoDB version it runs and compare it with 2026.08.1.Source: vulncheck.com
How do I fix CVE-2026-126278?
Upgrade NocoDB to version 2026.08.1 or later, which the listed range gives as the fixed version.Source: vulncheck.com