Summary
n8n: Authenticated code execution in the n8n Git node
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. - Restrict network egress from the n8n instance to limit the impact of arbitrary code execution.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
Authenticated n8n users with rights to create and execute workflows could achieve code execution on the n8n host. Using the Git node, under the default git security settings, by staging a crafted local repository, an attacker could cause git to run hooks, executing arbitrary commands as the n8n process user.
Both self-hosted and cloud instances are affected where authenticated users can create and execute workflows using the Git node.
Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.
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-RCV6-PVRJ-4XCG? GHSA-RCV6-PVRJ-4XCG is a high-severity OS command injection vulnerability in n8n (npm), affecting versions < 1.123.67. It is fixed in 1.123.67, 2.32.1, 2.31.5. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
- Which versions of n8n are affected by GHSA-RCV6-PVRJ-4XCG? n8n (npm) versions < 1.123.67 is affected.
- Is there a fix for GHSA-RCV6-PVRJ-4XCG? Yes. GHSA-RCV6-PVRJ-4XCG is fixed in 1.123.67, 2.32.1, 2.31.5. Upgrade to this version or later.
- Is GHSA-RCV6-PVRJ-4XCG exploitable, and should I be worried? Whether GHSA-RCV6-PVRJ-4XCG 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-RCV6-PVRJ-4XCG 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-RCV6-PVRJ-4XCG?
- Upgrade
n8nto 1.123.67 or later - Upgrade
n8nto 2.32.1 or later - Upgrade
n8nto 2.31.5 or later
- Upgrade