CVE-2026-86995: CWE-73: External Control of File Name or Path in n8n-io n8n
Affects n8n-io n8nSource CVE Database V5
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:NWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| n8n-ion8n | Affected
| Fixed in– |
GitHub Actionsn8n-io/n8npkg:github/n8n-io/n8nOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in n8n versions 1.123.76, 2.37.7, and 2.38.2. Users should upgrade to one of these versions or later to remediate the issue. No other mitigation or workaround is indicated. Patch status is confirmed by the vendor advisory.
Description
n8n is an open source workflow automation platform. Prior to 1.123.76, 2.37.7, and 2.38.2, the Git node validated the repository parameter for fetch or pull, but setUpstream wrote a branch..remote value into repository configuration without validating it. A later fetch or pull resolved the remote from that configuration instead of the checked parameter. An authenticated workflow editor could therefore point Git at any local repository readable by the n8n process and receive its contents through packages/nodes-base/nodes/Git/GenericFunctions.ts. This issue is fixed in versions 1.123.76, 2.37.7 and 2.38.2.
Impact
An authenticated user with workflow editing privileges can exploit this vulnerability to read contents from any local Git repository accessible by the n8n process. This could lead to unauthorized disclosure of sensitive information stored in local repositories. There is no indication of privilege escalation or remote code execution. The CVSS 4.0 base score is 5.3 (medium severity), reflecting network attack vector, low complexity, and low impact on confidentiality.
Summary
In n8n versions before 1.123.76, 2.37.7, and 2.38.2, the Git node validated the repository parameter for fetch or pull operations, but the setUpstream function wrote a branch.remote value into the repository configuration without validation. Subsequent fetch or pull commands resolved the remote from this configuration instead of the originally checked parameter. This flaw allows an authenticated workflow editor to direct Git commands at any local repository accessible by the n8n process and retrieve its contents, leading to potential unauthorized data exposure. The vulnerability is classified under CWE-73 (External Control of File Name or Path) and CWE-22 (Path Traversal).
Weaknesses
References
- github.com/n8n-io/n8n/security/advisories/GHSA-qgpw-8g46-w95v (opens in a new tab)
- github.com/n8n-io/n8n/releases/tag/[email protected] (opens in a new tab)
- github.com/n8n-io/n8n/releases/tag/[email protected] (opens in a new tab)
- github.com/n8n-io/n8n/releases/tag/[email protected] (opens in a new tab)