Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to n8n with low-privilege account
-
DeliveryConfigure Git node clone to a validated path
-
ExploitSwap validated directory for symlink (win TOCTOU race)
-
ExecutionClone malicious repo into community node directory
-
Persistn8n restart loads planted custom node
-
ImpactExecute arbitrary JavaScript on server
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
|
| Exploitation Conditions | Exploitation requires an authenticated n8n account with the ability to use the Git node's clone operation (CVSS PR:L), and the attacker must win a filesystem race: swap the validated clone target directory for a symlink in the interval between path validation and the clone write (CWE-367 TOCTOU). Success further depends on n8n's community/custom node loading being active so the planted repository in the community node directory is loaded and executed on the next server restart, and on the attacker being able to influence the clone path and control a repository. Limiting factors: authentication is mandatory (no unauthenticated path), the attack requirement AT:P and high complexity AC:H reflect that the race is not reliably won on a single try, and code execution is deferred until an n8n restart occurs - so instances that rarely restart or that disable community nodes materially reduce practical exploitability. |
| Impact | The vendor CVSS 4.0 vector (AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H, base 8.9) is internally consistent with the description: network-reachable, but requiring an authenticated low-privilege account (PR:L), a non-trivial exploit path (AC:H), and a race-window attack requirement (AT:P) that is not always winnable on the first attempt. Real-world priority is elevated by the full high impact to confidentiality, integrity, and availability plus a scope-changing effect (SC:H) - it converts an app-level account into host code execution - but tempered by the authentication requirement and the timing/race precondition, which favor a deliberate attacker over opportunistic mass exploitation. No EPSS score, KEV listing, or SSVC decision data was provided, so automatability and in-the-wild exploitation cannot be asserted; the absence of a public POC further suggests exploitation would currently be targeted rather than commodity. Net: a genuine high-severity RCE that warrants prompt patching wherever untrusted or numerous users hold n8n accounts, but not a drive-by unauthenticated worm. |
| Exploit ScenarioDerived | A low-privilege but authenticated n8n user builds a workflow using the Git node pointed at a hostile repository and configures a clone destination that passes path validation. In a tight loop, they win the TOCTOU race by swapping the validated directory for a symlink after the check but before the clone, causing the malicious repo to land in the community node directory; when n8n next restarts, it loads the planted node and executes the attacker's JavaScript on the server. No public POC is currently identified, and the race window plus AC:H means several attempts may be needed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Server-side remote code execution in n8n workflow automation (self-hosted and cloud) before 1.123.64, 2.29.8, and 2.30.1 lets authenticated users abuse a TOCTOU race in the Git node's clone operation to write a malicious repository into the community node directory, which n8n auto-loads and executes on the next restart. The flaw bypasses path validation by swapping a validated directory for a symlink before the clone runs, turning a low-privilege account into arbitrary JavaScript execution on the host. No public exploit identified at time of analysis; reported by VulnCheck.
RemediationAI
Upgrade to a fixed release: Vendor-released patch: n8n 1.123.64, 2.29.8, or 2.30.1 (choose the fixed version on your current branch), per advisory GHSA-g3r5-9h93-4j2c (https://github.com/n8n-io/n8n/security/advisories/GHSA-g3r5-9h93-4j2c); n8n Cloud is remediated by the vendor. Where immediate patching is not possible, reduce exposure by restricting who can create or run workflows using the Git node - limit accounts to trusted operators and remove Git node access from low-trust users, since exploitation requires an authenticated user driving that node. As compensating controls, disable or block loading of community/custom nodes (set the environment so community packages are not loaded at startup, e.g. do not enable community node execution) to break the load-and-execute step - trade-off: legitimate community nodes stop working - and run the n8n process as an unprivileged, containerized user with a read-only or tightly permissioned community node directory so a planted repository cannot be written or executed. Monitor the community node directory for unexpected repositories and audit Git node usage.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
n8n is a Node.js-based workflow automation platform whose Git node wraps clone/pull operations, and which supports 'community' (custom) nodes loaded from a designated directory at startup. The vulnerability is CWE-367 (Time-of-Check to Time-of-Use race): the clone target path is validated once, but between that check and the actual filesystem write the attacker replaces the checked directory with a symlink, so the clone lands outside the intended sandbox - specifically in the community node directory. Because n8n dynamically requires/executes JavaScript from community nodes when the process restarts, a planted repository containing hostile node code runs in the server's Node.js process. Affected CPE is cpe:2.3:a:n8n-io:n8n across the vulnerable version ranges.
Know when N8n gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Network-reachable via an authenticated low-priv account (PR:L); the TOCTOU race and deferred restart make it AC:H; escaping the app to run host JS is a scope change (S:C) with full C/I/A impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
n8n workflow automation (self-hosted and cloud versions) contains a critical remote code execution vulnerability that allows authenticated users to exploit a TOCTOU race condition in Git operations to execute arbitrary code on the host system. Organizations relying on n8n for mission-critical workflows face significant risk of insider exploitation or lateral movement following account compromise.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) restrict Git node access to administrators via RBAC in n8n; (2) network-isolate n8n deployments to prevent lateral movement; (3) enable comprehensive audit logging of all Git node operations and monitor for anomalous activity; (4) suspend Git node workflows until patches are released; (5) enforce multi-factor authentication on all n8n accounts; (6) regularly audit n8n role assignments and configurations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Remote code execution in n8n's workflow expression evaluation system allows an authenticated user with workflow creation
n8n workflow automation (through 1.121.2) allows authenticated users to execute arbitrary code via the n8n service, with
n8n workflow automation (1.65.0 to 1.121.0) allows unauthenticated file access through form-based workflows. A critical
n8n has a fifth critical RCE vulnerability (CVSS 9.9) in the Expression evaluator, enabling code execution through craft
Authenticated users who can create or modify an n8n workflow can achieve remote code execution on the n8n host by abusin
A prototype pollution vulnerability in the XML and GSuiteAdmin nodes of n8n workflow automation platform allows authenti
An authenticated user with workflow creation or modification privileges in n8n workflow automation platform can exploit
n8n-workflows Main Commit ee25413 allows attackers to execute a directory traversal via the download_workflow function w
Authenticated n8n users can hijack administrator accounts when LDAP authentication is enabled by manipulating their LDAP
The n8n package 0.218.0 for Node.js allows Escalation of Privileges. Rated high severity (CVSS 8.8), this vulnerability
SQL injection in n8n's Data Table Get node allows authenticated users with workflow modification permissions to execute
Authenticated users can exploit string formatting and exception handling in n8n's Python task executor to escape sandbox
EUVD-2026-47642
GHSA-725q-c4vp-q4cg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB