CriticalPublic exploit

n8n Expression Sandbox Escape RCE

IdentifiersCVE-2026-1470CWE-94

CVE-2026-1470 is a critical authenticated remote code execution vulnerability in n8n’s workflow Expression evaluation system. User-supplied JavaScript expressions used during workflow configuration are evaluated in a sandboxed context, but the sandbox enforcement is incomplete. Multiple supporting sources describe the root cause as an AST sandbox escape involving improper handling of JavaScript with statements and insufficient sanitization of the standalone constructor identifier. This allows crafted expressions to bypass the Expression sandbox, resolve to the JavaScript Function constructor, and execute arbitrary JavaScript in the context of the main n8n node. Publicly described proof-of-concept behavior includes using expression payloads in workflow parameters or blocks such as Edit Fields to reach Node.js runtime functionality and invoke modules such as child_process for OS command execution. Successful exploitation results in arbitrary code execution with the privileges of the n8n process.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An authenticated attacker who can create or modify workflows can achieve full remote code execution on the affected n8n instance’s main node. This can lead to complete compromise of the instance, including theft of credentials, API keys, environment variables, and other sensitive workflow data; unauthorized modification of workflows and automation logic; execution of arbitrary system commands; and potential pivoting into connected internal systems and third-party services accessible through n8n. Because n8n commonly holds access to business-critical integrations, exploitation may effectively provide broad organizational access beyond the application itself.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict workflow creation and modification permissions to fully trusted administrators only, and remove access for low-privilege or shared users who can configure expressions. Reduce exposure of the n8n UI and API by limiting access to trusted networks, enforcing strong authentication such as SSO/VPN, and applying IP allowlisting where feasible. Run n8n with least privilege and strong host isolation so compromise of the n8n process has reduced blast radius, e.g., non-root execution and container or VM isolation with restrictive security profiles. Continuous monitoring of workflow changes and suspicious command execution is also advisable.

Remediation

Patch, then assume compromise.

Upgrade n8n to a fixed release. Supporting content consistently states that CVE-2026-1470 is fixed in versions 1.123.17, 2.4.5, and 2.5.1, and that all earlier versions in the affected release lines are vulnerable. Self-hosted deployments should be updated immediately to the appropriate patched version for their branch. If using n8n Cloud, the available content indicates the issue has already been addressed there.

PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

N8nN8napplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

36 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

36 SOURCESView more in app

nuclei templates pull requestsNews

Apr 17, 2026

Add 5 CVE templates (Batch 5) - Passed 5-agent review by eyangfeng88-arch · Pull Request #15962 · projectdiscovery/nuclei-templates · GitHub

A remote code execution vulnerability affecting n8n via expressions.

cloudatg insightsNews

Feb 13, 2026

AI Development & Software Engineering | CloudATG

n8n eval injection vulnerability enabling authenticated RCE by bypassing expression safeguards.

jfrog researchNews

Feb 9, 2026

Software Vulnerabilities - JFrog Security Research

Remote code execution (RCE) in n8n via the Expression Node.

the hacker newsNews

Feb 2, 2026

⚡ Weekly Recap: Proxy Botnet, Office Zero-Day, MongoDB Ransoms, AI Hijacks & New Threats

Unknown (listed as a trending CVE affecting n8n; no technical details provided in the content).

+7 more in the timeline

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity25

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-1470

NVD

nvd.nist.gov/vuln/detail/CVE-2026-1470

MITRE CWE · CWE-94

cwe.mitre.org

Patch

github.com/n8n-io/n8n/commit/aa4d1e5825829182afa0ad5b81f602638f55fa04

Patch

research.jfrog.com/vulnerabilities/n8n-expression-node-rce