GHSA-g3r5-9h93-4j2c CVE-2026-65598 CVE-2026-71539

n8n: Race Condition in Git Clone Node Allows Authenticated Users to Achieve Remote Code Execution

High npm

Severity: 0.0 / 10; High · CVSS 4.0
Exploit chance (EPSS): 0.34%; Chance of exploitation in the next 30 days. Higher than 26.94% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Fix: 1.123.64; Upgrade n8n to this version or later

Description

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 NODES_EXCLUDE 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.

Affected versions

npm

Package	Vulnerable	Fixed in
n8n	`< 1.123.64`	`1.123.64`
n8n	`>= 2.30.0, < 2.30.1`	`2.30.1`
n8n	`>= 2.0.0-rc.0, < 2.29.8`	`2.29.8`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

n8n npm → `1.123.64`

npm

npm install n8n@1.123.64

yarn

yarn add n8n@1.123.64

pnpm

pnpm add n8n@1.123.64

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:L

Attack vector: Network
Attack complexity: High
Attack requirements: Present
Privileges required: Low
User interaction: None
Confidentiality (vulnerable system): High
Integrity (vulnerable system): High
Availability (vulnerable system): High
Confidentiality (subsequent systems): High
Integrity (subsequent systems): Low
Availability (subsequent systems): Low

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Weakness

CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.

How to prevent it

Implementation: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
Implementation: When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Architecture and Design: Limit the interleaving of operations on files from multiple processes.
Implementation, Architecture and Design: If you cannot perform operations atomically and you must share access to the resource between multiple processes or threads, then try to limit the amount of time (CPU cycles) between the check and use of the resource. This will not fix the problem, but it could make it more difficult for an attack to succeed.
Implementation: Recheck the resource after the use call to verify that the action was taken appropriately.
Architecture and Design: Ensure that some environmental locking mechanism can be used to protect resources effectively.
Implementation: Ensure that locking occurs before the check, as opposed to afterwards, such that the resource, as checked, is the same as it is when in use.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-65598

Packages

github.com/n8n-io/n8n

Timeline

Jul 22, 2026 Published
Oct 29, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-v98v-ff95-f3cp n8n Vulnerable to Remote Code Execution via Expression Injection	High Known exploited	Also affects n8n
GHSA-qgpw-8g46-w95v n8n: Git Node branch.<name>.remote Config Key Bypasses Sandbox Path Restriction, Enabling Local Git Repository Read	Medium	Also affects n8n
GHSA-65xw-2v52-jhxc n8n: Cross-User Active Workflow ID and Lifecycle Event Disclosure via Missing userId Filter	Medium	Also affects n8n
GHSA-pq6c-vh67-xpm3 n8n: Log Streaming Event Destinations Decrypt Generic-Auth Credentials Without Ownership Check	Medium	Also affects n8n
GHSA-cqr2-h44g-v75v n8n: Cross-Tenant Project-Member PII Disclosure via Missing Per-Project Scope Check on Role Assignment Endpoints	Medium	Also affects n8n
GHSA-pf83-w3f9-8m37 n8n: Disabled OIDC SSO Endpoints Remain Active and Issue Valid Sessions	Medium	Also affects n8n
GHSA-6xcw-7xm6-48c6 n8n: Expression Sandbox Escape via Shared Builtin Tampering and Code-Printer Injection Leads to Code Execution	High	Also affects n8n
GHSA-34ff-336r-5q23 n8n: Domain-Restriction Bypass via Unguarded Model-Search Endpoint in OpenAI Chat Model Node	Medium	Also affects n8n

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor