# CVE-2026-54687: n8n-nodes-sqlite3: Path traversal via user-controlled database file path (db_path parameter)

> Attackers can read, create, or overwrite files by manipulating the database path parameter in the n8n SQLite node.

- **Severity:** Medium 6.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-q7m3-rhxg-7vxr

## What is CVE-2026-54687?

CVE-2026-54687 is a medium-severity path traversal vulnerability in DangerBlack n8n-node-sqlite3, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54687?

2 open source packages ship an affected version, including n8n-nodes-sqlite3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `n8n-nodes-sqlite3` | npm | All versions | 1.0.0 |
| `n8n-nodes-sqlite3` | npm | All versions | 1.0.0 |

Products: Dangerblack N8n-Node-Sqlite3.

## How do I fix CVE-2026-54687?

Upgrade n8n-nodes-sqlite3 to 1.0.0 or later.

## Is CVE-2026-54687 being exploited?

There is no known exploitation of CVE-2026-54687 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54687 and fix it if it is affected.

What it is: CVE-2026-54687 is a medium-severity path traversal vulnerability in DangerBlack n8n-node-sqlite3, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-54687 in the wild and no public exploit code.

Affected packages and fixed versions:
- n8n-nodes-sqlite3 (npm): affected all versions; fixed in 1.0.0
- n8n-nodes-sqlite3 (npm): affected all versions; fixed in 1.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54687/ (Markdown: https://insights.sbomify.com/CVE-2026-54687/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54687
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54687
- OSV: https://osv.dev/vulnerability/CVE-2026-54687

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54687/
Summaries are generated and may contain mistakes; the official description above is the record.