CVE
NocoDB unauthorized database access via source connection cache
Affects NocoDB before 2026.08.1, where a base Creator can reach records in another base's external database. No vendor severity is given, only the CVSS score of 9.3. Fixed in 2026.08.1.
- 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. Attacker needs an authenticated account with the Creator role on one unrelated base. Attacker needs knowledge of the victim source id, which shared-view metadata exposes. The victim's connection must already be cached in the process handling the request.
Summary
NocoDB before 2026.08.1 contains an authorization bypass vulnerability that allows authenticated Creators to access another tenant's external database by reusing a victim source id when adding a source. Because NcConnectionMgrv2 caches connections by bare source id, attackers can reflect the victim's cached database schema and read, update, and insert records through their own base models.
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, 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 authenticated account with the Creator role on one unrelated base. Attacker needs knowledge of the victim source id, which shared-view metadata exposes. The victim's connection must already be cached in the process handling the request.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-130712 (NocoDB before 2026.08.1 Cross-Base Database Access via Source ID Collision), 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-130712 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.08.1
Fixed versions: 2026.08.1.
Conditions (all must be true for the bug to be hit):
- Attacker needs an authenticated account with the Creator role on one unrelated base. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-m8pf-2hc5-2cvc)
- Attacker needs knowledge of the victim source id, which shared-view metadata exposes. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-m8pf-2hc5-2cvc)
- The victim's connection must already be cached in the process handling the request. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-m8pf-2hc5-2cvc)
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-130712 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130712 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-m8pf-2hc5-2cvc
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-130712
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-130712"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- Posted on X by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.08.1
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-m8pf-2hc5-2cvc |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130712 |
| Record | NVD · CVE-2026-130712 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130712
Is CVE-2026-130712 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 user with the Creator role on one base can use the source ID of another base's external database to reflect that database's schema into their own base. They can then read, update and insert records in that database through their own models, even though they have no role on the victim base.Source: github.com
Which versions are affected by CVE-2026-130712?
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. The attack needs an authenticated account with the Creator role on an unrelated base, knowledge of the victim source ID (which shared-view metadata exposes), and the victim's connection already cached in the process handling the request. To check a deployment, compare the installed NocoDB version with 2026.08.1.Source: github.com
How do I fix CVE-2026-130712?
Upgrade NocoDB to 2026.08.1 or later, which is the listed fixed version. The sources do not name vendor patch IDs or a workaround.Source: github.com