CVE-2026-77084 is a high severity (8.8) command injection in n8n's Git node. The node ran certain repository-local git configuration values without neutralizing them, so a later Git node operation could run them as the n8n user. It needs a separate way to write files. Upgrade to 1.123.69, 2.33.4 or 2.34.1 or later.
What's affected
The record says n8n before 1.123.69, 2.x before 2.33.4, and 2.34.x before 2.34.1 are affected. GitHub's advisory lists the same range and says the patched versions are 1.123.69, 2.33.4 and 2.34.1 or later.
The component is the Git node. This is not reachable through the node's own configuration controls, and the record says it needs a separate file-write vulnerability elsewhere to plant the malicious value.
Where sources differ. The advisory scores this High 7.7 on CVSS 4.0, and the record's CVSS 3.1 score is different, so the two numbers describe the same flaw through different scoring models. The advisory's patch note names 1.123.67, 2.31.5 and 2.32.1 as fixed versions, while its affected range runs below 1.123.69, 2.33.4 and 2.34.1. That is inconsistent, so move to 1.123.69, 2.33.4 or 2.34.1 or later.
How to check if you're exposed
Find every n8n instance, including ones a team stood up on its own, and print the version:
n8n --version
docker exec <container> n8n --version
npm ls -g n8n
The first works where the CLI is installed, the second for a Docker container, the third for a global npm install. Compare with the patched versions: 1.123.69 on the 1.x line, 2.33.4 on 2.33, and 2.34.1 on 2.34. Also find workflows that use the Git node.
GitHub lists these temporary mitigations in the advisory:
- 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.
- Run the n8n process under a dedicated low-privilege user account, to limit the impact of any command execution.
GitHub is clear that they do not fully remediate the risk and are short-term measures. A dependency scan is the quickest way to find this kind of component across many projects. Safeguard's free in-browser scan at gold.safeguard.sh/scan checks your dependencies against known CVEs, and reachability analysis helps you separate libraries your code actually calls from ones that only sit in the tree.
What to do now
- Upgrade n8n to 1.123.69, 2.33.4, or 2.34.1 or later, whichever matches your release line.
- Until you can, apply the advisory's temporary mitigations, which GitHub says reduce risk without fully fixing it.
- Review who has accounts on the instance and what role each holds. Remove people who do not need access.
- Look through existing workflows for the feature involved, and confirm nothing unexpected has been added.
- Re-check the version afterward and record it.
Why it matters
Git repositories can carry configuration that names programs to run. The n8n Git node honored certain local configuration values without neutralizing them, so any later Git node operation on a repository holding a malicious value would execute it as the n8n process user. The record files it under CWE-78, OS command injection.
The record's 8.8 reads as network reachable and low complexity, but the advisory is explicit about a precondition: an attacker must first write a file somewhere else. That makes this a good example of chaining, where a modest file-write bug becomes code execution once a second issue exists. Fixing one half still closes the chain. The record does not mark it as a CISA KEV entry.
Quick check
Can this be exploited alone?
No. The advisory says it requires a separate file-write vulnerability elsewhere to plant the malicious value.
How can I turn the Git node off?
Add n8n-nodes-base.git to the NODES_EXCLUDE environment variable, if you do not need it.
Sources
Last reviewed: 18 October 2026.
