Skip to main content
Menu
CVEs

CVE

NocoDB row filter bypass exposes linked records in shared views

CVE-2026-130722Published Updated

6.9MediumCNA
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 shared-view relation endpoints because parent-record lookups apply only the primary key, not the view's row filter. Anonymous share-link holders can enumerate auto-increment primary keys against the has-many, many-to-many, one-to-many and link-to-another-record routes to read linked records of filtered-out rows.

cve.now Index

27Pcve.now Index 27 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 32 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-130722 (NocoDB before 2026.08.0 Shared View Row Filter Bypass via Linked Record 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-130722 (entry last updated 2026-11-18):
Affected:
- nocodb nocodb: fixed in 2026.08.0
Fixed versions: 2026.08.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130722 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130722 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-gpqx-c4rw-j4xm
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-130722
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-130722"}.

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-gpqx-c4rw-j4xm
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130722
RecordNVD · CVE-2026-130722

Corrections

None so far.

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

Questions about CVE-2026-130722

Is CVE-2026-130722 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

Which versions are affected by CVE-2026-130722?

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

How do I fix CVE-2026-130722?

Upgrade to a fixed version: 2026.08.0.Source: cve.now feed data

More CVEs