Summary
An authenticated user with base-create permission can attach a SQLite source pointing at
an arbitrary file on the NocoDB host, including NocoDB's own internal databases.
Details
The SQLite client and the base/integration create services accepted a caller-supplied
filename and passed it to fs.exists and fs.open('w') without restricting the location.
A user could point a source at noco.db, at a tenant database under nc_minimal_dbs/,
or at any writable path the NocoDB process can reach, and then read or overwrite its
contents through the regular table APIs.
Credit
This issue was reported by @Mouhebbenelwafi.
Impact
Disclosure and modification of NocoDB internal state, of other tenants' databases, and
of any file the NocoDB process can read or write. Authentication and base-create
permission are required.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
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-47385? CVE-2026-47385 is a medium-severity path traversal vulnerability in nocodb (npm), affecting versions <= 2026.05.0. It is fixed in 2026.05.1. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of nocodb are affected by CVE-2026-47385? nocodb (npm) versions <= 2026.05.0 is affected.
- Is there a fix for CVE-2026-47385? Yes. CVE-2026-47385 is fixed in 2026.05.1. Upgrade to this version or later.
- Is CVE-2026-47385 exploitable, and should I be worried? Whether CVE-2026-47385 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-47385 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-47385? Upgrade
nocodbto 2026.05.1 or later.