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

n8n Python Code node sandbox escape

IdentifiersCVE-2026-25115CWE-693· Protection Mechanism Failure

CVE-2026-25115 is a sandbox escape vulnerability in n8n, the open-source workflow automation platform, affecting versions prior to 2.4.8. The flaw resides in the Python Code node and allows an authenticated user to break out of the intended Python sandbox environment and execute code outside that security boundary. The advisory indicates exploitation is possible when Task Runners and the Python/code node are enabled. In default or non-isolated deployments, this can result in code execution in the main n8n execution context; when Task Runners are configured in external mode, the escape is constrained to the sidecar container rather than the primary n8n process.

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 a low-privileged authenticated user who can run code through the affected feature to escape the Python sandbox and execute code beyond the intended isolation boundary. This can lead to compromise of confidentiality, integrity, and availability, including arbitrary code execution in the n8n runtime context. In deployments using external Task Runners, impact is reduced because execution is limited to the sidecar container, but still represents a security boundary break and potential compromise of that runner environment.

Mitigation

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

If immediate patching is not possible, disable the Code node by adding n8n-nodes-base.code to the NODES_EXCLUDE environment variable. Also prefer N8N_RUNNERS_MODE=external so untrusted task execution occurs in an isolated sidecar container instead of the main n8n process, and configure Task Runners according to n8n guidance.

Remediation

Patch, then assume compromise.

Upgrade n8n to version 2.4.8 or later, which patches the Python Code node sandbox escape 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 activity4

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