Skip to main content
CVE-2026-1470VulnerabilityPublished

CVE-2026-1470: n8n · Eval Injection

Affects n8nSource CVE Database V5

0

Not known to be exploited · 20% EPSS · CVSS 9.9 Critical · fixed in 2.5.1 : patch n8n as a priority.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
20.4% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.1, 2.4.5, 1.123.17
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade n8n to 2.5.1, 2.4.5 or 1.123.17.

Affected software

ProductAffectedFixed in
npmn8npkg:npm/n8nOther threatsAffected
  • =0
  • =2.0.0
  • =2.5.0
Fixed in–
npmn8npkg:npm/n8nOther threatsAffected
  • <1.123.17
  • >=2.0.0 <2.4.5
  • >=2.5.0 <2.5.1
Fixed in
  • 1.123.17
  • 2.4.5
  • 2.5.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict access to n8n instances to trusted users only and enforce strong authentication mechanisms, including multi-factor authentication (MFA). 2. Monitor and audit workflow configurations for suspicious or unexpected expressions, especially those created or modified by users with elevated privileges. 3. Apply network segmentation to isolate n8n servers from sensitive backend systems to limit potential lateral movement. 4. If patches or updates become available from n8n, apply them promptly. 5. Consider disabling or restricting the use of dynamic expression evaluation features until a secure patch is deployed. 6. Implement runtime application self-protection (RASP) or Web Application Firewalls (WAF) with custom rules to detect and block suspicious payloads targeting expression evaluation. 7. Regularly review and rotate credentials used by n8n workflows to reduce risk from compromised accounts. 8. Conduct internal penetration testing focused on workflow expression injection to identify and remediate vulnerable configurations. 9. Educate developers and administrators on secure workflow design to avoid unsafe expression usage.

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.

References

Community reviews

Loading reviews…