CVE
NocoDB row filter bypass in shared view relation endpoints
Affects NocoDB before 2026.08.0 with a public shared view, where relation endpoints skip the view's row filters. Fixed in 2026.08.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026.08.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026.08.0.
Summary
NocoDB before 2026.08.0 contains an authorization bypass in its public shared-view relation endpoints, which verify that a parent record exists but not that it passes the view's row filters. Unauthenticated attackers holding a public share link can supply guessable auto-incrementing ids of filtered-out records to has-many, many-to-many, one-many, or link endpoints to read their child records.
Who should check
Teams running NocoDB before 2026.08.0 that publish shared views or public share links
“The public shared-view relation endpoints confirmed that the parent record named in the URL existed in the table”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2026.08.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-130729 (NocoDB before 2026.08.0 Row Filter Bypass via Shared View Relation Endpoints), 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-130729 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.08.0
Fixed versions: 2026.08.0.
Conditions (all must be true for the bug to be hit):
- A public shared view exposes its relation endpoints, which skip the view's row filters on the parent record. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-267g-6rgg-2qf9)
- The has-many, many-to-many, link, or one-many relation routes are reached. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-267g-6rgg-2qf9)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130729 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130729 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-267g-6rgg-2qf9
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-130729
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-130729"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- nocodb nocodb
fixed in 2026.08.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · nocodb/nocodb · Advisory GHSA-267g-6rgg-2qf9 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130729 |
| Record | NVD · CVE-2026-130729 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130729
Is CVE-2026-130729 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 public shared-view relation endpoints confirm that the parent record in the URL exists but do not apply the view's row filters. Child records linked to parent records the view hides can therefore be read using only the public share link.Source: github.com
Which versions are affected by CVE-2026-130729?
nocodb: before 2026.08.0.Source: cve.now feed data
Am I affected, and how do I check?
NocoDB versions before 2026.08.0 that expose a public shared view and reach its has-many, many-to-many, link, or one-many relation routes. To check, look at the NocoDB version in use and whether the view is shared publicly.Source: github.com
How do I fix CVE-2026-130729?
Upgrade NocoDB to 2026.08.0 or later, the listed fixed version.Source: github.com