How severe is GHSA-q7m3-rhxg-7vxr?

No CVSS score has been assigned to GHSA-q7m3-rhxg-7vxr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-q7m3-rhxg-7vxr?

GHSA-q7m3-rhxg-7vxr affects the following packages: n8n-nodes-sqlite3 (npm). Ecosystems affected: npm.

How do I fix GHSA-q7m3-rhxg-7vxr?

Update n8n-nodes-sqlite3 to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7m3-rhxg-7vxr is resolved across your whole dependency graph.

How do I detect GHSA-q7m3-rhxg-7vxr in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n-nodes-sqlite3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-q7m3-rhxg-7vxr if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-q7m3-rhxg-7vxr actively exploited in the wild?

No public exploit code has been indexed for GHSA-q7m3-rhxg-7vxr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-q7m3-rhxg-7vxr?

GHSA-q7m3-rhxg-7vxr has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-q7m3-rhxg-7vxr?

GHSA-q7m3-rhxg-7vxr is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-q7m3-rhxg-7vxr published, and has it been updated?

GHSA-q7m3-rhxg-7vxr was published on August 27, 2026 and was last updated on August 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

n8n-nodes-sqlite3 vulnerable to path traversal via user-controlled database file path (db_path parameter)GHSA-q7m3-rhxg-7vxr

Fix: DangerBlack/n8n-node-sqlite3#25

GHSA-q7m3-rhxg-7vxr is a Path Traversal vulnerability in n8n-nodes-sqlite3. A fix is available for n8n-nodes-sqlite3 — see the affected versions and patch details below.

Also known asCVE-2026-54687

Published

Aug 27, 2026

Updated

Aug 27, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-q7m3-rhxg-7vxr.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

n8n-nodes-sqlite3npm

171downloads / week

Description

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)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`n8n-nodes-sqlite3`	all versions	1.0.0`npm install n8n-nodes-sqlite3@1.0.0`

Affected Products

1 product · 1 configurations

Application

n8n-node-sqlite3dangerblack

1 version

1.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for n8n-nodes-sqlite3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update n8n-nodes-sqlite3 to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q7m3-rhxg-7vxr is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-q7m3-rhxg-7vxr in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

n8n-nodes-sqlite3 vulnerable to path traversal via user-controlled database file path (db_path parameter)GHSA-q7m3-rhxg-7vxr

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Affected versions

Patched version

Description

References

Credits

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-q7m3-rhxg-7vxr in your dependencies?