n8n: Authenticated code execution in the n8n Git node
n8n
- Severity
- High, CVSS 8.7
- CVSS vector
- CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Record
- GHSA-rcv6-pvrj-4xcg
- Affects
- n8n
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- July 22, 2026
- Source last modified
- July 22, 2026
Description
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.
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.
- 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.
Description quoted from the GitHub Advisory Database.
Who is affected
n8n is a platform for connecting apps and automating routine tasks with step-by-step workflows. This flaw affects both self-hosted and cloud setups of n8n where signed-in users can create and run workflows that use the Git building block (the part that lets a workflow work with code repositories), in versions that do not include the fix. A signed-in user with rights to create and run workflows could run any commands they choose on the computer that hosts n8n, with the same access as n8n itself. This works under the default Git security settings. This flaw is rated High.
What to do
- The person who installs or runs n8n for your organization should upgrade it to version
1.123.67,2.31.5or2.32.1, or any later version. - If an IT provider or vendor runs n8n for you, send them this advisory and ask when the update will be done.
- If upgrading is not immediately possible, restrict access to n8n to fully trusted users only, and restrict outgoing network access from n8n to limit the harm if commands are run.
- You can also turn off the Git building block by adding
n8n-nodes-base.gitto theNODES_EXCLUDEenvironment variable. These measures do not fully remove the risk and are only a short-term step until you upgrade.
Analysis written from the source record as of July 22, 2026 and reviewed before publishing.