CVE-2026-25115: n8n Python Sandbox Escape Vulnerability

n8n Updated 04 Feb 2026

Summary

04/02/2026
Yes i
Critical
9.4

CVE-2026-25115: n8n has a Python sandbox escape. Affects n8n versions < 2.4.8. Fixed in 2.4.8. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

n8n is an open-source workflow automation tool that allows users to connect various applications and services to automate tasks without needing extensive coding knowledge. It features a visual interface for creating workflows and supports various integrations. However, a vulnerability has been identified in its Python Code node, which can lead to unauthorized code execution outside the intended security boundaries.

Vulnerability Detail

The vulnerability in the n8n Python Code node allows authenticated users to escape the Python sandbox environment. This means that users can execute arbitrary code outside the intended security context, potentially leading to unauthorized access and control over the system. The issue arises when Task Runners are enabled, and Python is configured to run, allowing for exploitation by authenticated users. If the Task Runners mode is set to 'external', the risk is somewhat mitigated as the code executes in a separate sidecar container, but the potential for lateral movement remains a concern.

How To Fix

Latest published version: 2.44.6 as of 22 Oct 2026

npm install n8n@2.44.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.4.8

This is the first release that contains the fix.

npm install n8n@2.4.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate upgrading is not feasible, consider the following workarounds: 1. Disable the Code Node by adding 'n8n-nodes-base.code' to the 'NODES_EXCLUDE' environment variable. 2. Run Task Runners in external mode by setting 'N8N_RUNNERS_MODE=external' to isolate untrusted task code in a separate sidecar container.

Conclusion

The n8n Python sandbox escape vulnerability (CVE-2026-25115) poses a significant risk to users who have enabled Task Runners and Python Code nodes. It is crucial to update to the patched version or implement the recommended workarounds to secure your deployment.

See every vulnerability recorded for n8n →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 9.4, indicating a critical severity level.

Any deployment of n8n where Task Runners and Python Code nodes are enabled is affected, particularly if the environment variables are set to allow these features.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Implement the recommended workarounds, such as disabling the Code Node or running Task Runners in external mode to mitigate the risk until you can upgrade.

Yes, you can refer to the n8n documentation for Task Runners and blocking nodes for detailed configuration and security practices.

Related vulnerabilities

Recent vulnerabilities recorded for n8n.

How To Fix

Latest published version: 2.44.6 as of 22 Oct 2026

npm install n8n@2.44.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.4.8

This is the first release that contains the fix.

npm install n8n@2.4.8

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback