CVE-2026-86995: n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.123.76 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.37.7 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 2.38.2
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user who can edit workflows can exploit it. The attacker also needs the n8n process to have read access to the local Git repository they target.
Which n8n versions are affected?
Versions before 1.123.76, 2.37.7, and 2.38.2 are affected. The issue is fixed in 1.123.76, 2.37.7, and 2.38.2.
What information could be exposed?
An attacker can cause Git to read the contents of a local repository that is readable by the n8n process. Those contents can then be returned through the Git node's GenericFunctions.ts handling.