CVE-2026-27495
JavaScript Sandbox Escape in n8n Enables Host Compromise
Publication date: 2026-02-25
Last updated on: 2026-03-04
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| 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 ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the n8n workflow automation platform prior to versions 2.10.1, 2.9.3, and 1.123.22. An authenticated user who has permission to create or modify workflows can exploit a flaw in the JavaScript Task Runner sandbox to execute arbitrary code outside the sandbox boundary.
If the instance uses internal Task Runners (the default mode), this can lead to a full compromise of the host running n8n. If external Task Runners are used, the attacker might gain access to or affect other tasks executed on the Task Runner.
The vulnerability requires Task Runners to be enabled with the environment variable `N8N_RUNNERS_ENABLED=true`. It has been fixed in the specified versions, and upgrading is recommended to remediate the issue.
How can this vulnerability impact me? :
The impact of this vulnerability can be severe. On systems using internal Task Runners, an attacker exploiting this flaw can fully compromise the host machine running n8n, potentially gaining complete control over it.
On systems using external Task Runners, the attacker may gain unauthorized access to other tasks running on the Task Runner or disrupt their execution.
This could lead to unauthorized code execution, data breaches, service disruption, and other serious security consequences.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, users should upgrade n8n to versions 2.10.1, 2.9.3, or 1.123.22 or later, where the issue has been fixed.
If upgrading immediately is not possible, administrators should consider temporary mitigations such as limiting workflow creation and editing permissions to fully trusted users only.
Additionally, using external runner mode by setting `N8N_RUNNERS_MODE=external` can help limit the blast radius of an attack.
Note that these workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.