GHSA-GF29-4F56-R2JF
n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction
Overview
Description
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.gitto theNODES_EXCLUDEenvironment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Source: OX vulnerability database
Severity
HIGH
No CVSS vector in the source. Severity comes from the advisory.
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| npm | n8n | <1.123.67>=2.32.0, <2.32.1>=2.0.0-rc.0, <2.31.5 | 1.123.672.32.12.31.5 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/n8n-io/n8n
- github.com https://github.com/n8n-io/n8n/commit/f69dfc6dd2178a14ea1624d2e1d403c2e755042f
- github.com https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.67
- github.com https://github.com/n8n-io/n8n/releases/tag/n8n@2.31.5
- github.com https://github.com/n8n-io/n8n/releases/tag/n8n@2.32.1
- github.com https://github.com/n8n-io/n8n/security/advisories/GHSA-gf29-4f56-r2jf
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.