Path Traversal in n8n-nodes-sqlite3 (CVE-2026-54687)
Summary
Path traversal in n8n-nodes-sqlite3 (CVE-2026-54687). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.0.0 or later.
Original description
The description as published by the source.
n8n-nodes-sqlite3 is a node for operating a local SQLite database from n8n. Prior to 1.0.0, nodes/SqliteNode/v1/SqliteV1.node.ts exposes the db_path database file path as a node parameter that permits data expressions from upstream workflow input. A workflow author who maps untrusted input to db_path can allow a remote attacker to select which SQLite file the n8n process opens, enabling traversal outside the intended database location and potentially reading, creating, or overwriting files accessible to the process. This issue is fixed in version 1.0.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54687 has been found in n8n-nodes-sqlite3.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade n8n-nodes-sqlite3 to 1.0.0 or later.
If unsure, ask your IT team or search "n8n-nodes-sqlite3 CVE-2026-54687" on the vendor's site.
CVE-2026-54687 (n8n-nodes-sqlite3) — CWE-22 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in n8n-nodes-sqlite3.
Check the vendor advisory for the affected versions of n8n-nodes-sqlite3.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 1.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'n8n-nodes-sqlite3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'n8n-nodes-sqlite3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
n8n-nodes-sqlite3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade n8n-nodes-sqlite3 to 1.0.0ステージング環境で 1.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com