n8n has a Python sandbox escape

Impact

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 N8N_RUNNERS_ENABLED=true (default: false)
• Python was enabled N8N_PYTHON_ENABLED=true
• Code Node was enabled (default: true)

In case the N8N_RUNNERS_MODE 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.

Patches

This vulnerability is fixed in version 2.4.8 and later.

Workarounds

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. See the [n8n documentation](https://docs.n8n.io/hosting/configuration/task-runners/) for configuration details and required environment variables.

Resources

• n8n Documentation — Task Runners — external mode, setup guide, and environment configuration details
• n8n Documentation — Blocking nodes — how to globally disable specific nodes