Quick answers
- Is CVE-2026-47388 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47388 being exploited in the wild.
- How severe is CVE-2026-47388?
- Medium severity, with a CVSS score of 4, published 23 June 2026.
- Which products and versions are affected?
- nocodb (npm) <= 2026.05.0, ECOSYSTEM:introduced=0,fixed=2026.05.1.
- Is there a fix for CVE-2026-47388?
- Yes. nocodb (npm): upgrade to 2026.05.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-47388 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47388?
- Check whether you run nocodb (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- nocodb (npm): upgrade to 2026.05.1 or later
npm install nocodb@2026.05.1
Technical details
An authorization bypass (CWE-639) exists in NocoDB's Model Context Protocol (MCP) implementation. The `readAttachment` tool accepted user-supplied path or URL values and streamed files via the storage adapter without verifying if the file belonged to the requester's specific base or workspace. An attacker with a valid MCP token and knowledge of a specific attachment path could bypass ownership checks to read arbitrary files in shared storage. The vulnerability is resolved in version 2026.05.1 by implementing a lookup in `nc_file_references` to ensure the `base_id` matches the caller's context before streaming.
Affected products
- NocoDB NocoDB < 2026.05.1
Identifiers
- CVE-2026-47388
- GHSA-xxpj-q764-9r6q
Timeline
- 2026-06-04: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: NVD publication date