CVE
NocoDB authentication bypass via OAuth tokens in session handling
Affects NocoDB builds before 2026.10.1, and the Enterprise build's token exchange and socket handshake also accept OAuth access tokens. No vendor severity is given, so the CVSS score of 9.3 (critical) stands. Fixed in 2026.10.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.10.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB builds before 2026.10.1 (affected versions are below 2026.10.1). In the Enterprise build, the short-lived token exchange and the socket handshake also accept OAuth access tokens.
Summary
NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows OAuth token holders to act as full sessions because OAuth access tokens are signed with the instance JWT secret. Attackers can present a narrowly scoped OAuth token to the session strategy, short-lived-token exchange, or NocoSocket handshake to gain the granting user's full privileges.
Who should check
Teams running self-hosted NocoDB builds before 2026.10.1. Enterprise builds are also exposed through the short-lived token exchange and socket handshake.
“In the Enterprise build, the exchange in short-lived-token.strategy.ts”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB builds before 2026.10.1 (affected versions are below 2026.10.1). In the Enterprise build, the short-lived token exchange and the socket handshake also accept OAuth access tokens.Upgrade to a fixed version: 2026.10.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-130730 (NocoDB before 2026.10.1 OAuth Access Token Accepted as First-Party Session), 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-130730 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.1
Fixed versions: 2026.10.1.
Conditions (all must be true for the bug to be hit):
- NocoDB builds before 2026.10.1 (affected versions are below 2026.10.1). (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-xmfr-pc8j-4xh5)
- In the Enterprise build, the short-lived token exchange and the socket handshake also accept OAuth access tokens. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-xmfr-pc8j-4xh5)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-130730 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130730 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-xmfr-pc8j-4xh5
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-130730
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-130730"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.10.1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-xmfr-pc8j-4xh5 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130730 |
| Record | NVD · CVE-2026-130730 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130730
Is CVE-2026-130730 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?
An OAuth access token issued for a narrow scope could be used against first-party APIs with the full privileges of the user who granted it. This bypasses the scope restrictions of the consent flow.Source: github.com
Which versions are affected by CVE-2026-130730?
nocodb: before 2026.10.1.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB builds below 2026.10.1 are affected. In the Enterprise build, the short-lived token exchange and the socket handshake also accept OAuth access tokens. Compare the installed NocoDB version against 2026.10.1 to check the build.Source: github.com
How do I fix CVE-2026-130730?
Upgrade NocoDB to 2026.10.1 or later, which is the listed fixed version. The facts name no other patch or workaround.Source: github.com