CVE
NocoDB authorization bypass exposes internal metadata database
Affects NocoDB before 2026.10.0 when an account holds the Creator role, either on a base to add a data source or in a workspace to create a base. Fixed in 2026.10.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.10.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker needs an account with the Creator role, either on a base (to add a data source) or in a workspace (to create a base)
Summary
NocoDB before 2026.10.0 contains an improper access control vulnerability that allows Creator-role users to attach NocoDB's internal database by supplying is_meta and is_local flags. Attackers can create sources or bases with these flags to expose user, token and integration tables, then read and modify records including user roles.
Who should check
Teams running NocoDB before 2026.10.0 where users hold the Creator role and can add data sources or create bases.
“letting a user with the Creator role attach NocoDB's internal database to their base.”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.7/10CVSS 8.7, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Attacker needs an account with the Creator role, either on a base (to add a data source) or in a workspace (to create a base)Upgrade to a fixed version: 2026.10.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-130704 (NocoDB before 2026.10.0 Metadata Database Exposure via Client-Controlled Source Flags), 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-130704 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.10.0
Fixed versions: 2026.10.0.
Conditions (all must be true for the bug to be hit):
- Attacker needs an account with the Creator role, either on a base (to add a data source) or in a workspace (to create a base) (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-982h-vc99-prcr)
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-130704 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130704 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-982h-vc99-prcr
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-130704
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-130704"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- nocodb nocodb
fixed in 2026.10.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-982h-vc99-prcr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130704 |
| Record | NVD · CVE-2026-130704 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130704
Is CVE-2026-130704 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 account with the Creator role can expose NocoDB's internal tables inside its own base. It can then read them, including user accounts and the token and integration tables, and change those records, including user roles, through the same APIs.Source: github.com
Which versions are affected by CVE-2026-130704?
nocodb: before 2026.10.0.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.10.0 are affected. The attack needs an account with the Creator role, either on a base (to add a data source) or in a workspace (to create a base). Compare the installed NocoDB version with 2026.10.0 to check the version side.Source: github.com
How do I fix CVE-2026-130704?
Upgrade NocoDB to 2026.10.0 or later, which is the listed fixed version. The advisory data provided names no separate patch identifiers or workaround.Source: github.com