CVE-2026-25115: n8n is vulnerable to Python sandbox escape

Published Feb 4, 2026
·
Updated

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

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 NODESEXCLUDE 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

--- n8n has adopted CVSS 4.0 as primary score for all security advisories. CVSS 3.1 vector strings are provided for backward compatibility.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Other sources

n8n is an open source workflow automation platform. Prior to version 2.4.8, 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. This issue has been patched in version 2.4.8.

MITRE

Affected Software

3 affected componentsFixes available
n8n/n8n<2.4.8
npm/n8n<2.4.8
2.4.8
n8n N8n Node.js<2.4.8

Event History

Feb 4, 2026
CVE Published
via MITRE·04:48 PM
Data Sourced
via MITRE·04:48 PM
DescriptionWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·07:42 PM
Data Sourced
via GitHub·07:42 PM
DescriptionWeaknessAffected Software
Jun 19, 58090
Event
via FIRST·05:17 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-25115?

CVE-2026-25115 is considered a high severity vulnerability due to its potential for code execution outside the sandbox.

2

How do I fix CVE-2026-25115?

To mitigate CVE-2026-25115, upgrade n8n to version 2.4.8 or later.

3

Who is affected by CVE-2026-25115?

Only authenticated users leveraging the Python Code node in n8n versions prior to 2.4.8 are affected by CVE-2026-25115.

4

What could an attacker do with CVE-2026-25115?

An attacker could exploit CVE-2026-25115 to execute arbitrary code outside the Python sandbox, compromising the security of the system.

5

Is CVE-2026-25115 specific to certain installations of n8n?

Yes, CVE-2026-25115 specifically affects n8n installations that are running versions earlier than 2.4.8.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203