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
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.
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 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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| n8n | npm | < 2.4.8 | 2.4.8 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- Criticaln8n Has an Arbitrary File Read via Git Noden8n, n8n, n8n
- Criticaln8n: HTTP Request Node Pagination Prototype Pollution to RCEn8n, n8n, n8n
- Criticaln8n Has an XML Node Prototype Pollution Patch Bypassn8n, n8n, n8n
- Criticaln8n has XML Node Prototype Pollution that to RCEn8n, n8n, n8n
- Criticaln8n has Prototype Pollution in XML Webhook Body Parser that Leads to RCEn8n, n8n, n8n
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.