n8n · n8n
The n8n workflow automation platform has a flaw in its workflow expression evaluation system, where expressions supplied during workflow configuration may run in an execution context that is not sufficiently isolated from the underlying runtime. An attacker with only an authenticated account and no user interaction, able to supply expressions in a workflow, can execute arbitrary code with the privileges of the n8n process, which can lead to unauthorized access to sensitive data, modification of workflows, and system-level operations.
n8n is an open source workflow automation platform. Versions starting with 0.211.0 and prior to 1.120.4, 1.121.1, and 1.122.0 contain a critical Remote Code Execution (RCE) vulnerability in their workflow expression evaluation system. Under certain conditions, expressions supplied by authenticated users during workflow configuration may be evaluated in an execution context that is not sufficiently isolated from the underlying runtime. An authenticated attacker could abuse this behavior to execute arbitrary code with the privileges of the n8n process. Successful exploitation may lead to full compromise of the affected instance, including unauthorized access to sensitive data, modification of workflows, and execution of system-level operations. This issue has been fixed in versions 1.120.4, 1.121.1, and 1.122.0. Users are strongly advised to upgrade to a patched version, which introduces additional safeguards to restrict expression evaluation. If upgrading is not immediately possible, administrators should consider the following temporary mitigations: Limit workflow creation and editing permissions to fully trusted users only; and/or deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully eliminate the risk and should only be used as short-term measures.
First seen exploited 2 months after disclosure. Public exploit code (Metasploit) was available 6 months before disclosure.
CISA KEV listing is when exploitation was confirmed, not necessarily the first attack.
2 related vulnerabilities in the same code over 10 weeks. The latest fix listed for n8n is 2.4.0.
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
Requires authenticated user with workflow permissions
expressions supplied by authenticated users during workflow configuration
Arbitrary code execution via expression evaluation
execute arbitrary code with the privileges of the n8n process
CVE-specific rules are not available in this build. Search SigmaHQ ↗
These detect the technique in general, not this specific vulnerability.
Sigma rules © SigmaHQ, Detection Rule License 1.1; linked, not reproduced.
1 package in 1 ecosystem. Main package: n8n.
Upgrade to 1.121.1 or later
npm install n8n@1.121.1The first fix for CVE-2025-68613.
| If you run | Upgrade to |
|---|---|
| 1.121.0 up to 1.121.1 | 1.121.1 |
| 0.211.0 up to 1.120.4 Still affected on this line by CVE-2026-21858 (fixed in 1.121.0, a newer line). | 1.120.4 |
“Up to” means the second version is the fix and is not affected.
Reports are matched by finding the exact id CVE-2025-68613 in their text; nobody has reviewed the match. One passage is shown per report, at most 320 characters, linked to the original.
Mentions the CVE; no further detail.
Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.