n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction
Authenticated users of n8n with workflow create or execute permissions could exploit a vulnerability in the Git node's fetch, pull, or push-tags operations to bypass repository path restrictions. This allows them to access local git repositories outside the intended sandbox, potentially reading files and history. The issue is fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1 and later. Temporary mitigations include restricting access to trusted users and disabling the Git node, but these do not fully resolve the risk.
AI Analysis
Technical Summary
The vulnerability in n8n affects the Git node's fetch, pull, and push-tags operations, which do not enforce repository-path containment checks as strictly as clone and push operations. Authenticated users with workflow create or execute rights can configure an allowlisted remote to point to a local path outside the sandbox, enabling them to pull arbitrary local git repositories into the workspace. This bypasses intended sandbox restrictions and allows reading of repository files and history. The issue is tracked as CWE-22 (Path Traversal) and has been addressed in n8n versions 1.123.67, 2.31.5, and 2.32.1.
Potential Impact
An authenticated user with workflow create or execute permissions can bypass sandbox path restrictions in the Git node, potentially accessing and reading arbitrary local git repositories on the host system. This could lead to unauthorized disclosure of sensitive files and git history within those repositories.
Mitigation Recommendations
A fix is available in n8n versions 1.123.67, 2.31.5, and 2.32.1 and later; users should upgrade to these versions or newer to remediate the vulnerability. If immediate upgrade is not possible, administrators should restrict n8n instance access to fully trusted users and disable the Git node by adding 'n8n-nodes-base.git' to the NODES_EXCLUDE environment variable. These workarounds do not fully mitigate the risk and should only be used temporarily.
n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction
Description
Authenticated users of n8n with workflow create or execute permissions could exploit a vulnerability in the Git node's fetch, pull, or push-tags operations to bypass repository path restrictions. This allows them to access local git repositories outside the intended sandbox, potentially reading files and history. The issue is fixed in n8n versions 1.123.67, 2.31.5, and 2.32.1 and later. Temporary mitigations include restricting access to trusted users and disabling the Git node, but these do not fully resolve the risk.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in n8n affects the Git node's fetch, pull, and push-tags operations, which do not enforce repository-path containment checks as strictly as clone and push operations. Authenticated users with workflow create or execute rights can configure an allowlisted remote to point to a local path outside the sandbox, enabling them to pull arbitrary local git repositories into the workspace. This bypasses intended sandbox restrictions and allows reading of repository files and history. The issue is tracked as CWE-22 (Path Traversal) and has been addressed in n8n versions 1.123.67, 2.31.5, and 2.32.1.
Potential Impact
An authenticated user with workflow create or execute permissions can bypass sandbox path restrictions in the Git node, potentially accessing and reading arbitrary local git repositories on the host system. This could lead to unauthorized disclosure of sensitive files and git history within those repositories.
Mitigation Recommendations
A fix is available in n8n versions 1.123.67, 2.31.5, and 2.32.1 and later; users should upgrade to these versions or newer to remediate the vulnerability. If immediate upgrade is not possible, administrators should restrict n8n instance access to fully trusted users and disable the Git node by adding 'n8n-nodes-base.git' to the NODES_EXCLUDE environment variable. These workarounds do not fully mitigate the risk and should only be used temporarily.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gf29-4f56-r2jf
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a6150cc9c2644c7f8da0168
Added to database: 07/22/2026, 23:22:52 UTC
Last enriched: 07/22/2026, 23:28:07 UTC
Last updated: 07/22/2026, 23:28:07 UTC
Views: 2
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.