CVE
NocoDB authentication bypass in OAuth token exchange
Affects NocoDB versions before 2026.08.1 when a confidential OAuth client is used with PKCE-issued authorization codes. Fixed in 2026.08.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.08.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB versions before 2026.08.1 (the OAuth token endpoint in oauth-token.service.ts). The target OAuth client is a confidential client, and the authorization code was issued with PKCE.
- 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? →
- 13/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? →
- Specific setups only
- 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 an authentication bypass vulnerability in oauth-token.service.ts that treats PKCE as a substitute for confidential client authentication, skipping client secret verification when omitted. Attackers holding a captured authorization code and PKCE verifier can mint access tokens and 60-day refresh tokens for a confidential client without knowing its secret.
Who should check
Teams running self-hosted NocoDB before 2026.08.1 that use OAuth confidential clients with the authorization code grant.
Read the source excerpt
“NocoDB before 2026.08.1 contains an authentication bypass vulnerability in oauth-token.service.ts”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.08.1 (the OAuth token endpoint in oauth-token.service.ts). The target OAuth client is a confidential client, and the authorization code was issued with PKCE.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-126276 (NocoDB before 2026.08.1 Client Authentication Bypass via OAuth Token Exchange), 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-126276 (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 (the OAuth token endpoint in oauth-token.service.ts). (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-client-authentication-bypass-via-oauth-token-exchange)
- The target OAuth client is a confidential client, and the authorization code was issued with PKCE. (source: https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-client-authentication-bypass-via-oauth-token-exchange)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-126276 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126276 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-4cx5-q9xx-5pgj
- https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-client-authentication-bypass-via-oauth-token-exchange
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-126276
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-126276"}.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-126276
Is CVE-2026-126276 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?
The OAuth token endpoint in NocoDB can issue access tokens and 60-day refresh tokens for a confidential client without the client secret. An attacker who holds an authorization code and its matching PKCE verifier can obtain these tokens in the name of that client.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126276?
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, and the issue concerns the OAuth token exchange in oauth-token.service.ts. To check, compare your installed NocoDB version against 2026.08.1 and see whether any OAuth clients are configured as confidential clients.Source: vulncheck.com, github.com
How do I fix CVE-2026-126276?
Upgrade NocoDB to version 2026.08.1 or later, which is the listed fixed version. No vendor patch identifiers or workaround are named in the facts.Source: vulncheck.com, github.com