CVE-2026-65598: n8n before 1.123.64 Remote Code Execution via Git Clone

Published Jul 22, 2026
·
Updated

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.

Patches Users should upgrade to the patched version once available 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 NODESEXCLUDE environment 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.

Other sources

n8n before 1.123.64, 2.29.8, and 2.30.1 contains a TOCTOU race condition in the Git node's clone operation that allows authenticated users to bypass path restrictions by swapping a directory for a symlink after the path is validated but before the clone runs. This lets an attacker plant a crafted repository in the community node directory, which n8n loads as a custom node on the next restart, executing arbitrary JavaScript on the server. Both self-hosted and cloud instances are affected.

MITRE

Affected Software

10 affected componentsFixes available
n8n n8n<1.123.64, =2.29.8, =2.30.1
npm/n8n>=2.0.0-rc.0<2.29.8
2.29.8
npm/n8n>=2.30.0<2.30.1
2.30.1
npm/n8n<1.123.64
1.123.64
n8n N8n Node.js<1.123.64
n8n N8n Node.js<1.123.64
n8n N8n Node.js>=2.0.0<2.29.8
n8n N8n Node.js>=2.0.0<2.29.8
n8n N8n Node.js=2.30.0
n8n N8n Node.js=2.30.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.29.8
  2. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 2.30.1
  3. Upgrade

    Upgrade npm/n8n to a version that resolves this vulnerability.

    Fixed in 1.123.64
  4. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 1.123.64
  5. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.29.8
  6. Upgrade

    Upgrade n8n to a version that resolves this vulnerability.

    Fixed in 2.30.1
  7. Configuration

    Temporarily mitigate by disabling the Git node: add `n8n-nodes-base.git` to the `NODES_EXCLUDE` environment variable.

    n8n NODES_EXCLUDE = n8n-nodes-base.git
  8. Compensating control

    Temporarily mitigate by restricting n8n instance access to fully trusted users only.

  9. Compensating control

    Temporarily mitigate by restricting network egress from the n8n instance to prevent connections to attacker-controlled git repositories.

Event History

Jul 22, 2026
CVE Published
via MITRE·11:21 AM
Data Sourced
via MITRE·11:21 AM
DescriptionWeakness
Data Sourced
via NVD·12:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:18 PM
Affected Software
Advisory Published
via GitHub·05:56 PM
Data Sourced
via GitHub·05:56 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-65598?

CVE-2026-65598 has a severity rating of high, with a CVSS score of 8.9.

2

How does CVE-2026-65598 affect n8n?

CVE-2026-65598 allows an authenticated user to exploit a TOCTOU race condition during the Git clone operation, leading to remote code execution.

3

What is a key risk of CVE-2026-65598?

The key risk of CVE-2026-65598 is that it enables attackers to bypass path restrictions and execute malicious code in the n8n community node directory.

4

How can I fix CVE-2026-65598?

To fix CVE-2026-65598, upgrade n8n to version 1.123.64 or later, where the vulnerability is addressed.

5

Who can be affected by CVE-2026-65598?

Any authenticated user of n8n versions prior to 1.123.64 may be affected by CVE-2026-65598.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203