Summary
n8n: Git Node fetch/pull/pushTags Operations Bypass Sandbox Path Restriction
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.
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.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is GHSA-GF29-4F56-R2JF? GHSA-GF29-4F56-R2JF is a high-severity path traversal vulnerability in n8n (npm), affecting versions < 1.123.67. It is fixed in 1.123.67, 2.32.1, 2.31.5. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of n8n are affected by GHSA-GF29-4F56-R2JF? n8n (npm) versions < 1.123.67 is affected.
- Is there a fix for GHSA-GF29-4F56-R2JF? Yes. GHSA-GF29-4F56-R2JF is fixed in 1.123.67, 2.32.1, 2.31.5. Upgrade to this version or later.
- Is GHSA-GF29-4F56-R2JF exploitable, and should I be worried? Whether GHSA-GF29-4F56-R2JF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-GF29-4F56-R2JF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-GF29-4F56-R2JF?
- Upgrade
n8nto 1.123.67 or later - Upgrade
n8nto 2.32.1 or later - Upgrade
n8nto 2.31.5 or later
- Upgrade