CVE-2026-27494: n8n has Arbitrary File Read via Python Code Node Sandbox Escape

Published Feb 25, 2026
·
Updated

Impact 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 N8NRUNNERSENABLED=true.

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

Workarounds

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 NODESEXCLUDE environment variable.

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

Other sources

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 N8NRUNNERSENABLED=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 NODESEXCLUDE environment variable. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

NVD

Affected Software

6 affected componentsFixes available
npm/n8n>=2.10.0<2.10.1
2.10.1
npm/n8n>=2.0.0<2.9.3
2.9.3
npm/n8n<1.123.22
1.123.22
n8n N8n Node.js<1.123.22
n8n N8n Node.js>=2.0.0<2.9.3
n8n N8n Node.js>=2.10.0<2.10.1

Event History

Feb 25, 2026
Advisory Published
via GitHub·09:22 PM
Data Sourced
via GitHub·09:22 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·10:08 PM
Data Sourced
via MITRE·10:08 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 PM
Affected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-27494?

CVE-2026-27494 is considered a high severity vulnerability due to the risk of remote code execution (RCE) and data exfiltration.

2

How do I fix CVE-2026-27494?

To remediate CVE-2026-27494, upgrade to n8n version 2.10.1, 2.9.3, or 1.123.22, depending on your currently installed version.

3

Who is affected by CVE-2026-27494?

CVE-2026-27494 affects authenticated users with permission to create or modify workflows in certain versions of n8n.

4

What are the potential impacts of CVE-2026-27494?

The impact of CVE-2026-27494 includes the ability to exfiltrate file contents and perform remote code execution from within the application.

5

What versions of n8n are vulnerable to CVE-2026-27494?

Versions of n8n between 2.0.0 and 2.9.3, and version 2.10.0 are vulnerable to CVE-2026-27494.

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