Skip to main content
Menu
CVEs

CVE

NocoDB authorization bypass in shared view row lookups

Affects NocoDB before 2026.08.0 when a shared view uses a row filter that excludes some records. Fixed in 2026.08.0.

CVE-2026-130727Published Updated Summary written by a model

8.7HighCNA
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 vulnerability in public shared-view endpoints that fetch records by primary key without applying the view's row filter. Anonymous share link holders can enumerate sequential primary keys on link, has-many, and attachment download endpoints to read excluded records' linked data and download their attachments.

Who should check

Teams running NocoDB before 2026.08.0 that publish shared views or share links to anonymous recipients.

“Affected versions < 2026.08.0”

github.com

cve.now Index

29Pcve.now Index 29 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · 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 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 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-130727 (NocoDB before 2026.08.0 Shared View Row Filter Bypass via Primary Key Lookup), 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-130727 (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):
- NocoDB versions before 2026.08.0 are affected. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-xjxh-mq5w-mpq6)
- Shared view with a row filter that excludes some records; the attacker holds the share link. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-xjxh-mq5w-mpq6)
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-130727 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130727 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-xjxh-mq5w-mpq6
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-130727
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-130727"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • nocodb nocodb

    fixed in 2026.08.0

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · nocodb/nocodb · Advisory GHSA-xjxh-mq5w-mpq6
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130727
RecordNVD · CVE-2026-130727

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130727

Is CVE-2026-130727 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 anonymous holder of a share link can enumerate sequential primary keys to reach records that the shared view's row filter excludes. They can then read those records' linked-record data and download their attachment files.Source: github.com

Which versions are affected by CVE-2026-130727?

nocodb: before 2026.08.0.Source: cve.now feed data

Am I affected, and how do I check?

NocoDB versions before 2026.08.0 are affected, but only where a shared view has a row filter that excludes some records. To check, compare the installed NocoDB version with 2026.08.0 and review whether any shared view uses a row filter.Source: github.com

How do I fix CVE-2026-130727?

Upgrade NocoDB to 2026.08.0 or later, which is the fixed version in the sources.Source: github.com

More CVEs