CVE-2026-65598GHSA-G3R5-9H93-4J2C
n8n before 1.123.64 Remote Code Execution via Git Clone
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.123.64, 2.30.1, 2.29.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- n8n-io n8n
fixed in 1.123.64
- n8n-io n8n
From 2.30.0 · fixed in 2.30.1
- n8n-io n8n
From 2.0.0-rc.0 · fixed in 2.29.8
- n8nnpm
fixed in 1.123.64
- n8nnpm
From 2.30.0 · fixed in 2.30.1
- n8nnpm
From 2.0.0-rc.0 · fixed in 2.29.8