Skip to main content
Menu
CVEs

CVE

NocoDB authorization bypass in shared view row filters

Affects NocoDB versions before 2026.08.0 that use shared views, where excluded rows can be reached through attachments and linked records. Fixed in 2026.08.0.

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

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2026.08.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affected NocoDB versions before 2026.08.0. The attachment vector applies under NC_SECURE_ATTACHMENTS=true, where no raw path-based download route exists. A shared view link is required, and a view password where one is configured.

Summary

NocoDB before 2026.08.0 contains an authorization bypass vulnerability that allows anonymous share link holders to access records excluded by a shared view's row filter, because the read-by-primary-key path ignores the view's filters. Attackers can request the public attachment-download or nested-link listing routes with a record id to mint signed download URLs for hidden files and read linked-record data.

Who should check

Teams running NocoDB before 2026.08.0 that share views via public links, especially those with row filters hiding records or using secure attachments.

“Affected versions < 2026.08.0”

github.com

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure15/25Specific setups only, CISA rates it automatable
  • 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

What to do

  • Check whether your setup matches what the bug needs.

    Affected NocoDB versions before 2026.08.0. The attachment vector applies under NC_SECURE_ATTACHMENTS=true, where no raw path-based download route exists. A shared view link is required, and a view password where one is configured.
  • 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-130718 (NocoDB before 2026.08.0 Shared View Row Filter Bypass via Attachment Download), 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-130718 (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):
- Affected NocoDB versions before 2026.08.0. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-vxw5-9pjh-rq53)
- The attachment vector applies under NC_SECURE_ATTACHMENTS=true, where no raw path-based download route exists. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-vxw5-9pjh-rq53)
- A shared view link is required, and a view password where one is configured. (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-vxw5-9pjh-rq53)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130718 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130718 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-vxw5-9pjh-rq53
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-130718
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-130718"}.

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-vxw5-9pjh-rq53
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130718
RecordNVD · CVE-2026-130718

Corrections

None so far.

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

Questions about CVE-2026-130718

Is CVE-2026-130718 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?

Someone holding an anonymous share link can access records that a shared view's row filter excludes. They can also get working download links for files attached to those records and read linked-record data from them.Source: github.com

Which versions are affected by CVE-2026-130718?

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. The attachment path applies when NC_SECURE_ATTACHMENTS=true, and the attack needs a shared view link plus the view password where one is configured. Check the installed version and whether NC_SECURE_ATTACHMENTS is set to true.Source: github.com

How do I fix CVE-2026-130718?

Upgrade to NocoDB 2026.08.0 or later, the first version outside the affected range. The advisory names no patch identifiers.Source: github.com

More CVEs