CVE-2026-86995: CWE-73: External Control of File Name or Path in n8n-io n8n
A vulnerability in n8n workflow automation platform prior to versions 1.123.76, 2.37.7, and 2.38.2 allows an authenticated workflow editor to access contents of any local repository readable by the n8n process. This occurs because the Git node's setUpstream function writes an unvalidated branch remote value into repository configuration, which is later used by fetch or pull operations. The issue is fixed in the specified versions.
AI Analysis
Technical 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).
Potential 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.
Mitigation Recommendations
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.
CVE-2026-86995: CWE-73: External Control of File Name or Path in n8n-io n8n
Description
A vulnerability in n8n workflow automation platform prior to versions 1.123.76, 2.37.7, and 2.38.2 allows an authenticated workflow editor to access contents of any local repository readable by the n8n process. This occurs because the Git node's setUpstream function writes an unvalidated branch remote value into repository configuration, which is later used by fetch or pull operations. The issue is fixed in the specified versions.
CVSS v4.0
Score 5.3medium
Affected software
pkg:github/n8n-io/n8nRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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).
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-08T16:44:23.781Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa13d6bacd9273b49346a86
Added to database: 09/09/2026, 11:05:15 UTC
Last enriched: 09/09/2026, 11:09:37 UTC
Last updated: 09/09/2026, 12:07:12 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.