Summary
n8n-nodes-sqlite3 vulnerable to path traversal via user-controlled database file path (db_path parameter)
Affected versions
< 1.0.0
Patched version
1.0.0
Description
In versions prior to 1.0.0, the SQLite node accepted the database file
path as a direct node parameter visible and editable in the workflow.
A workflow author who mapped untrusted user input to the db_path field
could allow an attacker to control which file was opened by SQLite,
potentially enabling path traversal to read or overwrite arbitrary
files accessible to the n8n process.
The vulnerability requires the workflow author to explicitly wire
untrusted input to the db_path parameter, so it does not affect
standalone deployments where only trusted users author workflows.
However, in multi-tenant or user-facing n8n deployments the risk
is elevated.
Fixed in v1.0.0 by moving the database path into a credential
(v2 node architecture), which is stored server-side and not
controllable by workflow input data.
References
- Fix commit: 145a887
- Introduced credential-based path: v2 node
Credits
dyingman1 (role: Reporter)
Impact
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-54687? CVE-2026-54687 is a medium-severity path traversal vulnerability in n8n-nodes-sqlite3 (npm), affecting versions < 1.0.0. It is fixed in 1.0.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of n8n-nodes-sqlite3 are affected by CVE-2026-54687? n8n-nodes-sqlite3 (npm) versions < 1.0.0 is affected.
- Is there a fix for CVE-2026-54687? Yes. CVE-2026-54687 is fixed in 1.0.0. Upgrade to this version or later.
- Is CVE-2026-54687 exploitable, and should I be worried? Whether CVE-2026-54687 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-54687 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-54687? Upgrade
n8n-nodes-sqlite3to 1.0.0 or later.