Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

n8n JavaScript Task Runner sandbox escape

IdentifiersCVE-2026-27495CWE-94· Improper Control of Generation of…

CVE-2026-27495 is a critical sandbox escape vulnerability in n8n's JavaScript Task Runner. In n8n versions prior to 2.10.1, 2.9.3, and 1.123.22, an authenticated user who has permission to create or modify workflows can exploit a code injection flaw in the JavaScript Task Runner sandbox to execute arbitrary code outside the intended sandbox boundary. The issue affects deployments where Task Runners are enabled via N8N_RUNNERS_ENABLED=true. On instances using the default internal Task Runner mode, successful exploitation can lead to arbitrary code execution on the underlying n8n host. On instances using external Task Runners, exploitation may impact the runner environment and other tasks executed there.

Share:
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.

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.

Successful exploitation allows an authenticated workflow editor to break out of the JavaScript Task Runner sandbox and run arbitrary code beyond the intended isolation boundary. In the default internal runner configuration, this can result in full compromise of the n8n host. In external runner mode, the attacker may gain access to or interfere with other tasks executed on the Task Runner, expanding impact beyond a single workflow execution context.

Mitigation

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

If immediate patching is not possible, restrict workflow creation and editing permissions to fully trusted users only. Where feasible, use external runner mode by setting N8N_RUNNERS_MODE=external to reduce the blast radius compared with the default internal runner mode. These measures are temporary only and do not fully remediate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade n8n to a fixed version: 2.10.1, 2.9.3, or 1.123.22, or any later release that includes the patch. This is the primary remediation for the vulnerability.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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.

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.
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 signatures

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 activity6

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