AI agent vulnerability · n8n

GHSA-gf29-4f56-r2jf: n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction

highCVSS 4.0 7.1

Impact Authenticated n8n users with workflow create/execute rights could use the Git node's fetch, pull, or push-tags operations to bypass the repository-path containment checks that already protected clone and push.

Published Jul 22, 2026

Affected packages

n8n

Ecosystem: npm
Affected: < 1.123.67
Fixed in: 1.123.67
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: >= 2.32.0, < 2.32.1
Fixed in: 2.32.1
Check: npm ls n8n

n8n

Ecosystem: npm
Affected: >= 2.0.0-rc.0, < 2.31.5
Fixed in: 2.31.5
Check: npm ls n8n

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Impact

Authenticated n8n users with workflow create/execute rights could use the Git node's fetch, pull, or push-tags operations to bypass the repository-path containment checks that already protected clone and push. By pointing an allowlisted remote configuration value at a local path outside the intended sandbox, an attacker could pull an arbitrary local git repository into the workspace and subsequently read its files and history.

Patches

The issue has been fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1. 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.

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

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