CVE-2026-1470: n8n Unsafe Workflow Expression Evaluation Allows Remote Code Execution

Should you act?

High exploit likelihood

EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
• EPSS 20.7%, percentile 98: FIRST’s model estimates a 20.7% chance of exploitation activity in the next 30 days, higher than 98% of all scored CVEs (very high). EPSS is a probability, not a verdict.
• Needs an account (low (any account)). Exposure depends on who can log in.
• Only applies if your dependency tree includes n8n (npm) < 1.123.17, fixed in 1.123.17; n8n (npm) >= 2.0.0, < 2.4.5, fixed in 2.4.5; n8n (npm) >= 2.5.0, < 2.5.1, fixed in 2.5.1. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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.

Weakness type: CWE-95.

Product: n8n (npm) · Assigned by: JFROG · Published: 2026-01-27

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: low (any account)
• User interaction: none
• Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
• FIRST EPSS (model of 2026-10-21): 20.68% probability of exploitation activity in the next 30 days; percentile 98.

Timeline

• 2026-01-27 — CVE record last updated
• 2026-01-27 — CVE record published by JFROG
• 2026-01-27 — GitHub-reviewed advisory GHSA-5xrp-6693-jjx9 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

1. github.com github.com

Vulnerability records

1. GitHub Advisory GHSA-5xrp-6693-jjx9 github.com
2. CVE.org record CVE-2026-1470 cve.org
3. NVD entry CVE-2026-1470 nvd.nist.gov

Other references from the CVE record and advisory

1. research.jfrog.com research.jfrog.com
2. github.com github.com
3. github.com github.com

Critical npm advisories · Today’s Security Digest