CVE-2026-27495: n8n has a Sandbox Escape in its JavaScript Task Runner

Published Feb 25, 2026
·
Updated

Impact An authenticated user with permission to create or modify workflows could exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary.

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 one of these versions 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. - Use external runner mode (N8NRUNNERSMODE=external) to limit the blast radius.

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

Resources - n8n Documentation — Task Runners

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 exploit a vulnerability in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary. 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 one of these versions 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 use external runner mode (N8NRUNNERSMODE=external) to limit the blast radius. 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:23 PM
Data Sourced
via GitHub·09:23 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·10:10 PM
Data Sourced
via MITRE·10:10 PM
DescriptionWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 PM
Affected Software
Mar 23, 58145
Event
via FIRST·01:15 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-27495?

CVE-2026-27495 has a high severity due to its potential for arbitrary code execution by authenticated users.

2

How do I fix CVE-2026-27495?

To fix CVE-2026-27495, upgrade n8n to version 2.10.1, 2.9.3, or 1.123.22 or later.

3

What types of users are affected by CVE-2026-27495?

Authenticated users with permissions to create or modify workflows are affected by CVE-2026-27495.

4

In which versions of n8n is CVE-2026-27495 present?

CVE-2026-27495 is present in n8n versions prior to 2.10.1, 2.9.3, and 1.123.22.

5

What is a potential impact of CVE-2026-27495?

The potential impact of CVE-2026-27495 includes executing arbitrary code outside the sandbox of the JavaScript Task Runner.

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