CVE
NocoDB authorization bypass in MCP token middleware
NocoDB versions before 2026.09.0 let a user with Viewer access on one base read another base's metadata, including its table list and member emails. Fixed in 2026.09.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.09.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. NocoDB versions before 2026.09.0 (affected versions < 2026.09.0). The bug is in the base-scoped request middleware that reads an MCP token id from the route or query string; the same code is present in Community and Enterprise editions.
Summary
NocoDB before 2026.09.0 contains an authorization bypass vulnerability in extract-ids.middleware.ts that allows authenticated users to resolve roles against another base by supplying an MCP token id in the query string. Attackers with Viewer access on one base can mint an MCP token and pass its id to read another base's metadata, including table lists and member email addresses.
Who should check
Teams running NocoDB before 2026.09.0, including Community and Enterprise editions, where users hold Viewer access on at least one base.
“Affected versions < 2026.09.0”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
NocoDB versions before 2026.09.0 (affected versions < 2026.09.0). The bug is in the base-scoped request middleware that reads an MCP token id from the route or query string; the same code is present in Community and Enterprise editions.Upgrade to a fixed version: 2026.09.0.
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-130711 (NocoDB before 2026.09.0 Cross-Base Authorization Bypass via MCP Token Identifier), 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-130711 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.09.0
Fixed versions: 2026.09.0.
Conditions (all must be true for the bug to be hit):
- NocoDB versions before 2026.09.0 (affected versions < 2026.09.0). (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4m8g-w724-935g)
- The bug is in the base-scoped request middleware that reads an MCP token id from the route or query string; the same code is present in Community and Enterprise editions. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-4m8g-w724-935g)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130711 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130711 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-4m8g-w724-935g
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-130711
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-130711"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.09.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-4m8g-w724-935g |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130711 |
| Record | NVD · CVE-2026-130711 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130711
Is CVE-2026-130711 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 bug in the base-scoped request middleware lets an authenticated user with Viewer access on one base read another base's metadata, including its table list and base user roster with member email addresses, without any role on the target base. The advisory says writes did not follow.Source: github.com
Which versions are affected by CVE-2026-130711?
nocodb: before 2026.09.0.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.09.0 are affected, in both the Community and Enterprise editions, because the same middleware code is present in both. To check a version, look at the NocoDB version shown in the application or in the deployed image tag.Source: github.com
How do I fix CVE-2026-130711?
Upgrade NocoDB to 2026.09.0 or later, which is the fixed version listed for this vulnerability.Source: github.com