Summary
n8n: Race Condition in Git Clone Node Allows Authenticated Users to Achieve Remote Code Execution
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 prevent connections to attacker-controlled git repositories.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Impact
A TOCTOU race condition in the Git node's clone operation lets an authenticated user bypass its path restrictions by swapping a directory for a symlink after the path is validated but before the clone runs. This plants a crafted repository in the community node directory, which n8n loads as a custom node on the next restart, and since nodes execute JavaScript, this yields arbitrary code execution on the server.
Both self-hosted and cloud instances are affected, where authenticated users can create and run workflows using the Git node.
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
Users should upgrade to the patched version once available to remediate the vulnerability.
Frequently Asked Questions
- What is CVE-2026-65598? CVE-2026-65598 is a high-severity security vulnerability in n8n (npm), affecting versions < 1.123.64. It is fixed in 1.123.64, 2.30.1, 2.29.8.
- Which versions of n8n are affected by CVE-2026-65598? n8n (npm) versions < 1.123.64 is affected.
- Is there a fix for CVE-2026-65598? Yes. CVE-2026-65598 is fixed in 1.123.64, 2.30.1, 2.29.8. Upgrade to this version or later.
- Is CVE-2026-65598 exploitable, and should I be worried? Whether CVE-2026-65598 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 CVE-2026-65598 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 CVE-2026-65598?
- Upgrade
n8nto 1.123.64 or later - Upgrade
n8nto 2.30.1 or later - Upgrade
n8nto 2.29.8 or later
- Upgrade