Free AI Safety Workshop — in collaboration with explainx.aiSave your seat
AgentbeamBeta
AI agent vulnerability · n8n

CVE-2026-86995: n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read

mediumCVSS 4.0 5.3GHSA-qgpw-8g46-w95v

Impact The Git node validated the repository that a fetch or pull targeted, but setUpstream wrote a branch. .remote value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read…

Published Sep 10, 2026

Affected packages

n8n

Ecosystem
npm
Affected
< 1.123.76
Fixed in
1.123.76
Check
npm ls n8n

n8n

Ecosystem
npm
Affected
>= 2.38.0, < 2.38.2
Fixed in
2.38.2
Check
npm ls n8n

n8n

Ecosystem
npm
Affected
>= 2.0.0, < 2.37.7
Fixed in
2.37.7
Check
npm ls n8n

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

The Git node validated the repository that a fetch or pull targeted, but setUpstream wrote a branch.<name>.remote value into the repository's own configuration without validating it. A subsequent fetch or pull resolved the remote from that configuration rather than from the checked parameter, so an authenticated user with workflow-edit permission could point it at any local repository the n8n process could read and receive its contents. The patch validates the branch remote configuration on the same terms as the repository parameter.

Patches

The issue has been 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 vulnerability.

Workarounds

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Restrict n8n instance access to fully trusted users only.
  • Disable the Git node by adding n8n-nodes-base.git to the NODES_EXCLUDE environment variable.
  • Ensure the n8n process runs under a dedicated low-privilege OS user account to limit the scope of any filesystem access.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Credited to Masofgon.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More n8n vulnerabilities

All n8n entries