GitHub Advisoryadvisory · npm

GHSA-xxpj-q764-9r6q NocoDB: Missing Ownership Check in MCP Attachment Read

LOW Published 2026-06-05 Modified 2026-07-20 Official page ↗
Aliases
CVE-2026-47388
Ecosystem
npm
Packages
nocodb
Severity
Low
CVSS 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
Weaknesses
CWE-639
Reviewed
2026-06-05

Affected packages

• npm nocodb: < 2026.05.1 → fixed in 2026.05.1

Description

Summary 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. Details The MCP `readAttachment` tool accepts caller-supplied `path`/`url` values and streams the file via the storage adapter. The handler now looks up the path in `nc_file_references` and requires a non-deleted row whose `base_id` matches the caller's MCP context before streaming; otherwise it returns `Attachment is not accessible from this MCP context`. The lookup tolerates both `download/uploads/...` and `uploads/...` styles. Impact Arbitrary read against shared storage scoped to attachments the caller's MCP context should not see. Exploitation requires an MCP token and a known attachment path. Credit This issue was reported by @helwor-01.

Related

Alias · CVE (1)

  • CVE-2026-47388 NocoDB is software for building databases as spreadsheets. vulnerability

Weakness · CWE (1)

  • CWE-639 Authorization Bypass Through User-Controlled Key weakness

References