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 innc_file_references and requires a non-deleted row whose base_id matches the
caller's MCP context before streaming; otherwise it returnsAttachment is not accessible from this MCP context. The lookup tolerates bothdownload/uploads/... and uploads/... styles.
Credit
This issue was reported by @helwor-01.
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-47388? CVE-2026-47388 is a low-severity security vulnerability in nocodb (npm), affecting versions <= 2026.05.0. It is fixed in 2026.05.1.
- Which versions of nocodb are affected by CVE-2026-47388? nocodb (npm) versions <= 2026.05.0 is affected.
- Is there a fix for CVE-2026-47388? Yes. CVE-2026-47388 is fixed in 2026.05.1. Upgrade to this version or later.
- Is CVE-2026-47388 exploitable, and should I be worried? Whether CVE-2026-47388 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-47388 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-47388? Upgrade
nocodbto 2026.05.1 or later.