CVE
NocoDB attachment disclosure in shared views via IDOR
Affects NocoDB before 2026.08.0 in community builds, unlicensed self-hosted Enterprise, or on MySQL/SQLite data sources. 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 information disclosure vulnerability that allows unauthenticated attackers to access attachments of filtered-out records through the shared view attachment-download endpoint. Attackers holding a public share link can enumerate sequential primary keys to obtain signed download paths for files on records the view's row filter excludes.
Who should check
Teams running NocoDB before 2026.08.0 with shared views, especially on community builds, unlicensed self-hosted Enterprise, or MySQL/SQLite data sources.
“Community and unlicensed self-hosted Enterprise deployments on any database”
cve.now Index
- 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-130723 (NocoDB before 2026.08.0 Shared View Attachment Disclosure via Record ID Enumeration), 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-130723 (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 community builds, unlicensed self-hosted Enterprise, or MySQL/SQLite data sources (the fallback read path) (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-879g-fg46-vpv2)
- A shared view with a public share link and an attachment column, with the target record excluded by the view's row filter (source: https://github.com/nocodb/nocodb/security/advisories/GHSA-879g-fg46-vpv2)
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-130723 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130723 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-879g-fg46-vpv2
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-130723
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-130723"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
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-879g-fg46-vpv2 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130723 |
| Record | NVD · CVE-2026-130723 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130723
Is CVE-2026-130723 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?
A shared view with a public share link and an attachment column can let an anonymous caller obtain signed download paths for files attached to records that the view's row filter excludes. Those files include documents and images.Source: github.com
Which versions are affected by CVE-2026-130723?
nocodb: before 2026.08.0.Source: cve.now feed data
Am I affected, and how do I check?
Versions before 2026.08.0 are affected in community builds, unlicensed self-hosted Enterprise deployments, and setups using MySQL or SQLite data sources. To check a setup, look at the edition and the database type the deployment uses.Source: github.com
How do I fix CVE-2026-130723?
Upgrade NocoDB to 2026.08.0 or later.Source: github.com