Skip to content
Fencer Intel
critical 9.9

CVE-2026-1470 in the critical feed json

Authenticated users can bypass the Expression sandbox mechanism to achieve full remote code execution on n8n’s main node.

published 9mo ago modified 4mo ago also EUVD-2026-4839 , GHSA-5xrp-6693-jjx9

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
20.4%
EPSS 20.4% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm n8n 1.123.17, 2.4.5, 2.5.1
  • n8n n8n 1.123.17, 2.4.5, 2.5.1

Is CVE-2026-1470 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
9mo ago

Exploit prediction

20.40% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • research.jfrog.com https://research.jfrog.com/vulnerabilities/n8n-expression-node-rce/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm n8n
<1.123.17
>=2.0.0, <2.4.5
>=2.5.0, <2.5.1
1.123.17
2.4.5
2.5.1

Classification

Weakness
  • CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.