# CVE-2026-130725: NocoDB before 2026.10.0 IDOR via Attachment Field Paths


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-q43c-vfw7-f9xm, GHSA-v279-4cwv-mrcj

## What is CVE-2026-130725?

CVE-2026-130725 is a medium-severity vulnerability in nocodb, published on 18 Nov 2026. 

### Official description

NocoDB before 2026.10.0 contains an insecure direct object reference vulnerability that allows authenticated users to obtain signed download URLs for other bases' attachments by storing foreign attachment paths in their own rows via prepareNocoData. Attackers with write access to an attachment column can have _convertAttachmentType or the attachment download endpoint sign the foreign path, reading cross-base files despite secure attachment mode.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-130725?


## How do I fix CVE-2026-130725?

Upgrade nocodb to 2026.10.0 or later. The advisory says that version fixes it.

## Is CVE-2026-130725 being exploited?

There is no known exploitation of CVE-2026-130725 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130725 and fix it if it is affected.

What it is: CVE-2026-130725 is a medium-severity vulnerability in nocodb, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130725 in the wild and no public exploit code.

Affected product: nocodb. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130725/ (Markdown: https://insights.sbomify.com/CVE-2026-130725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130725
- OSV: https://osv.dev/vulnerability/CVE-2026-130725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130725/
Summaries are generated and may contain mistakes; the official description above is the record.
