Quick answers
- Is CVE-2026-47385 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-47385 being exploited in the wild.
- How severe is CVE-2026-47385?
- 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-47385?
- 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-47385 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-47385?
- 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
A path traversal vulnerability exists in NocoDB's SQLite source integration. The application accepts a user-supplied filename and passes it directly to file system operations (fs.exists and fs.open) without proper validation or path restriction. An authenticated attacker with 'base-create' permissions can provide a path to internal files, such as 'noco.db' or tenant databases in 'nc_minimal_dbs/'. Once attached as a source, the attacker can use standard table APIs to read or overwrite the contents of these files. This issue is resolved in version 2026.05.1.
Affected products
- NocoDB NocoDB < 2026.05.1
Identifiers
- CVE-2026-47385
- GHSA-wvqj-9wv4-7ff5
Timeline
- 2026-06-04: advisory: GitHub Security Advisory published
- 2026-06-23: disclosed: CVE published to NVD