CVE-2026-54687: N8n nodes sqlite3 Path Traversal Vulnerability

MODERATE
Advisory Identifier: GHSA-q7m3-rhxg-7vxr
CWE-22
Published
Advisory Summary

CVE-2026-54687 is a MODERATE path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting N8n nodes sqlite3 libraries in the npm ecosystem. The issue involves n8n-nodes-sqlite3 vulnerable to path traversal via user-controlled database file path (db_path parameter). Remediation is available by upgrading affected packages to version 1.0.0.

CVE-2026-54687 at a Glance

CVE Identifier CVE-2026-54687
GHSA Identifier GHSA-q7m3-rhxg-7vxr
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product N8n nodes sqlite3
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-54687

To remediate this vulnerability, upgrade all affected N8n nodes sqlite3 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

n8n-nodes-sqlite3 fixed: 1.0.0
npm install n8n-nodes-sqlite3@1.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls n8n-nodes-sqlite3

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-54687, inspect your project dependencies using npm:

npm ls n8n-nodes-sqlite3

Analyze the terminal output to locate any version of N8n nodes sqlite3 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.0), your application is affected.

Note: The npm ls n8n-nodes-sqlite3 command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In N8n nodes sqlite3, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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)

CVE-2026-54687 Affected N8n nodes sqlite3 Versions

1 component(s)
Fixed Versions:
1.0.0
Product / Package Ecosystem Affected Versions Fixed Version
n8n-nodes-sqlite3
npm
< 1.0.0
1.0.0

References

Frequently Asked Questions

What is CVE-2026-54687?
CVE-2026-54687 is a security vulnerability in N8n nodes sqlite3 involving n8n-nodes-sqlite3 vulnerable to path traversal via user-controlled database file path (db_path parameter) under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which N8n nodes sqlite3 versions are affected?
Affected versions include releases prior to 1.0.0 across affected packages: n8n-nodes-sqlite3.
What version fixes CVE-2026-54687?
Upgrading to 1.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is n8n-nodes-sqlite3 affected?
Yes, n8n-nodes-sqlite3 is affected in releases prior to 1.0.0. Upgrade your dependency to 1.0.0 or later.
What CWE is associated with CVE-2026-54687?
CVE-2026-54687 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check npm dependencies for CVE-2026-54687?
Run the dependency tree command: 'npm ls n8n-nodes-sqlite3'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q7m3-rhxg-7vxr",
  "modified" : "2026-08-27T17:06:55Z",
  "published" : "2026-08-27T17:06:55Z",
  "aliases" : [ "CVE-2026-54687" ],
  "summary" : "n8n-nodes-sqlite3 vulnerable to path traversal via user-controlled database file path (db_path parameter)",
  "details" : "## Affected versions\n< 1.0.0\n\n## Patched version\n1.0.0\n\n## Description\nIn versions prior to 1.0.0, the SQLite node accepted the database file\npath as a direct node parameter visible and editable in the workflow.\nA workflow author who mapped untrusted user input to the db_path field\ncould allow an attacker to control which file was opened by SQLite,\npotentially enabling path traversal to read or overwrite arbitrary\nfiles accessible to the n8n process.\n\nThe vulnerability requires the workflow author to explicitly wire\nuntrusted input to the db_path parameter, so it does not affect\nstandalone deployments where only trusted users author workflows.\nHowever, in multi-tenant or user-facing n8n deployments the risk\nis elevated.\n\nFixed in v1.0.0 by moving the database path into a credential\n(v2 node architecture), which is stored server-side and not\ncontrollable by workflow input data.\n\n## References\n- Fix commit: 145a887\n- Introduced credential-based path: v2 node\n\n## Credits\ndyingman1 (role: Reporter)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "n8n-nodes-sqlite3"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/DangerBlack/n8n-node-sqlite3/security/advisories/GHSA-q7m3-rhxg-7vxr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DangerBlack/n8n-node-sqlite3/pull/25"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/DangerBlack/n8n-node-sqlite3/commit/145a8876ff12375813bdcd4ae4fe78f460c53a98"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/DangerBlack/n8n-node-sqlite3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-27T17:06:55Z",
    "nvd_published_at" : null
  }
}