UTC
Critical

n8n has a Python sandbox escape

CVE-2026-25115 · GHSA-8398-gmmx-564h · published 2026-02-04 · updated 2026-03-25

Severity
Critical
CVSS score
9.9
Chance of exploitation (EPSS)
0.58%
Fixed in
2.4.8
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

A vulnerability in the Python Code node allows authenticated users to break out of the Python sandbox environment and execute code outside the intended security boundary. Only authenticated users are able to execute code through Task Runners. This issue affected any deployment in which the following conditions were met: Task Runners were enabled using N8NRUNNERSENABLED=true (default: false) Python was enabled N8NPYTHONENABLED=true Code Node was enabled (default: true) In case the N8NRUNNERSMODE is set to external (default: internal) the sandbox escape is limited to the sidecar container with lower risk for lateral movement. In that case a lower high severity is more appropriate.

What to do

Upgrade n8n to 2.4.8 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

This vulnerability is fixed in version 2.4.8 and later.

If you cannot upgrade yet

If an immediate upgrade cannot be applied, the following hardening steps are recommended: Disable the Code Node by adding n8n-nodes-base.code to the NODES_EXCLUDE environment variable Prefer external mode for isolation: run Task Runners in external mode so that untrusted task code executes in a separate sidecar container rather than within the main n8n process. This configuration significantly reduces the risk of in-process memory disclosure caused by unsafe buffer allocations.In external mode, a launcher manages Task Runner processes in a dedicated sidecar environment, separate from the primary n8n instance.

Affected
PackageRegistryAffectedFixed in
n8nnpm< 2.4.82.4.8

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].