CVE-2026-27494
Received Received - Intake
Python Sandbox Escape in n8n Code Node Enables Remote Code Execution

Publication date: 2026-02-25

Last updated on: 2026-03-05

Assigner: GitHub, Inc.

Description
n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, an authenticated user with permission to create or modify workflows could use the Python Code node to escape the sandbox. The sandbox did not sufficiently restrict access to certain built-in Python objects, allowing an attacker to exfiltrate file contents or achieve RCE. On instances using internal Task Runners (default runner mode), this could result in full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other task executed on the Task Runner. Task Runners must be enabled using `N8N_RUNNERS_ENABLED=true`. The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Users should upgrade to this version or later to remediate the vulnerability. If upgrading is not immediately possible, administrators should consider the following temporary mitigations. Limit workflow creation and editing permissions to fully trusted users only., and/or disable the Code node by adding `n8n-nodes-base.code` to the `NODES_EXCLUDE` environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-25
Last Modified
2026-03-05
Generated
2026-06-16
AI Q&A
2026-02-26
EPSS Evaluated
2026-06-15
NVD
CVE-2026-27494
EUVD
EUVD-2026-8757
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
n8n n8n to 1.123.22 (exc)
n8n n8n From 2.0.0 (inc) to 2.9.3 (exc)
n8n n8n From 2.10.0 (inc) to 2.10.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-497 The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability affects the n8n workflow automation platform prior to versions 2.10.1, 2.9.3, and 1.123.22. An authenticated user with permission to create or modify workflows could exploit the Python Code node to escape the sandbox environment. The sandbox did not sufficiently restrict access to certain built-in Python objects, which allowed the attacker to exfiltrate file contents or achieve remote code execution (RCE).

On instances using internal Task Runners (the default mode), this could lead to full compromise of the n8n host. On instances using external Task Runners, the attacker might gain access to or impact other tasks executed on the Task Runner.

The issue has been fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22. Temporary mitigations include limiting workflow creation and editing permissions to fully trusted users and disabling the Code node by adding it to the NODES_EXCLUDE environment variable, though these do not fully remediate the risk.

Impact Analysis

If exploited, this vulnerability can allow an attacker with workflow creation or modification permissions to escape the Python sandbox and execute arbitrary code.

On systems using internal Task Runners, this could result in full compromise of the host running n8n, potentially allowing the attacker to control the entire system.

On systems using external Task Runners, the attacker might gain access to or interfere with other tasks running on the Task Runner, potentially disrupting operations or accessing sensitive data.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability immediately, users should upgrade n8n to versions 2.10.1, 2.9.3, or 1.123.22 or later, where the issue is fixed.

If upgrading is not immediately possible, administrators should consider the following temporary mitigations:

  • Limit workflow creation and editing permissions to fully trusted users only.
  • Disable the Code node by adding 'n8n-nodes-base.code' to the NODES_EXCLUDE environment variable.

Note that these workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-27494. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart