CVE-2026-130729
7.5HighPublished 18 Nov 2026 · NVD status: Deferred · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on confidentiality
- Weakness
- CWE-639
What an attacker gets
Unauthenticated attackers can read sensitive child records by guessing auto-incrementing IDs via public shared-view links. Attackers only need access to a public share URL to exploit this.
Root cause
The application verifies the parent record exists but fails to apply the view's row-level security filters when accessing linked child records.
Affected versions
NocoDB versions before 2026.08.0
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Fix & remediation
Upgrade to NocoDB 2026.08.0 or later. If you cannot upgrade immediately, disable public shared views that contain sensitive linked records.
$ npm install nocodb@2026.08.0AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.