N8n: Improper Neutralization of Directives in Dynamically Evaluated Code
CVE-2026-1470 is a critical-severity improper neutralization of directives in dynamically evaluated code vulnerability in N8n, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 1.123.17, 2.4.5 as the first without the flaw, so updating N8n to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 20.4% chance of exploitation within 30 days, which is in the top 2.47% of all scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update N8n to 1.123.17 or 2.4.5, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| N8n | N8n | before 1.123.17; 2.0.0 up to, but not including, 2.4.5; 2.5.0 | 1.123.17, 2.4.5 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (jfrog.com).
Official description
n8n contains a critical Remote Code Execution (RCE) vulnerability in its workflow Expression evaluation system. 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Directives in Dynamically Evaluated Code
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. eval).
How developers prevent this class of flaw
- If possible, refactor your code so that it does not need to use eval() at all.
- For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures, so the python documentation discourages use of ast.literal_eval() on untrusted data.
More Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities (CWE-95)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other vulnerabilities in N8n
- 8.8 High severity
- 7.4 High severity
- 8.8 High severity
- 7.7 High severity
- 9.6 Critical severity
- 9.9 Critical severity
Recent Improper Neutralization of Directives in Dynamically Evaluated Code vulnerabilities
- 9.8 Critical severity
- 9.9 Critical severity
- 10.0 Critical severity
- 8.8 High severity
- 9.3 Critical severity
- 8.0 High severity
Spotted an error? Tell us.