GHSA-pf2q-pxhf-hgmw: n8n Path-Confinement Bypass Vulnerability
MODERATEGHSA-pf2q-pxhf-hgmw is a MODERATE path-confinement bypass vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting n8n libraries in the npm ecosystem. The issue involves path-confinement bypass in computer-use search_files allows reading files outside the base directory. Remediation is available by upgrading affected packages to version 2.32.1, 2.31.5.
GHSA-pf2q-pxhf-hgmw at a Glance
How to Fix GHSA-pf2q-pxhf-hgmw
To remediate this vulnerability, upgrade all affected n8n dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install n8n@2.32.1
npm install n8n@2.31.5
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls n8n
How to Check if You Are Affected
To determine whether your Node.js application is affected by GHSA-pf2q-pxhf-hgmw, inspect your project dependencies using npm:
npm ls n8n
Analyze the terminal output to locate any version of n8n in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.32.1), your application is affected.
Note: The npm ls n8n 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, 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
GHSA-pf2q-pxhf-hgmw Affected n8n Versions
2 component(s)References
Frequently Asked Questions
What is GHSA-pf2q-pxhf-hgmw?
Which n8n versions are affected?
What version fixes GHSA-pf2q-pxhf-hgmw?
Is n8n affected?
What CWE is associated with GHSA-pf2q-pxhf-hgmw?
How can I check npm dependencies for GHSA-pf2q-pxhf-hgmw?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pf2q-pxhf-hgmw",
"modified" : "2026-07-22T22:13:36Z",
"published" : "2026-07-22T22:13:36Z",
"aliases" : [ ],
"summary" : "n8n: Path-Confinement Bypass in computer-use search_files Allows Reading Files Outside the Base Directory",
"details" : "## Impact\n\nThe component `@n8n/computer-use` file-search tool confined searches to a configured base directory. A crafted search pattern could bypass the confinement check and expand to locations outside that directory, causing the tool to return the names and contents of files anywhere the daemon's OS user could read. Any deployment where an actor could influence the tool's search input was affected; the result was disclosure of arbitrary local files outside the intended sandbox.\n\n## Patches\n\nThe issue has been fixed in n8n versions 2.31.5 and 2.32.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\n\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict n8n instance access to fully trusted users only.\n- Disable or remove AI agent workflows that use the `computer-use` package until the instance is patched.\n- Ensure the n8n process runs under a dedicated low-privilege user account to limit the files accessible outside the sandbox.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.32.0"
}, {
"fixed" : "2.32.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "n8n"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.31.5"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/security/advisories/GHSA-pf2q-pxhf-hgmw"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/n8n-io/n8n"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5"
}, {
"type" : "WEB",
"url" : "https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-22T22:13:36Z",
"nvd_published_at" : null
}
}