CVE-2026-47388: NocoDB: Missing Ownership Check in MCP Attachment Read
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.
Published Jun 5, 2026 · Updated Jul 20, 2026
Affected packages
nocodb
- Ecosystem
- npm
- Affected
- <= 2026.05.0
- Fixed in
- 2026.05.1
- Check
npm ls nocodb
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to helwor-01.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-53927
NocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL
medium5.1No fixJun 17, 2026CVE-2026-53928
NocoDB: Refresh Tokens Persist Through Password Recovery
medium6.3No fixJun 17, 2026CVE-2026-53929
NocoDB: Stored Cross-Site Scripting via Secure Attachment
medium5.1No fixJun 17, 2026CVE-2026-53930
NocoDB: Server-Side Request Forgery via Base Migration URL
medium5.1No fixJun 17, 2026CVE-2026-53931
NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint
medium6.9No fixJun 17, 2026CVE-2026-47279
NocoDB: Hidden LTAR Column Exposure in Public Shared-View Relation Endpoints
medium6.9Jun 5, 2026
