Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.4
n8n Task Runner Sandbox Escape Allows Code Execution
CVE-2026-27495
GHSA-jjpj-p2wh-qf23
Summary
A malicious user with workflow editing permissions can execute unauthorized code on the server, potentially taking control of the entire system. This affects n8n instances using internal Task Runners. To fix, update to n8n version 2.10.1 or later. If a quick update isn't possible, limit editing permissions to trusted users or switch to external runner mode.
What to do
- Update GitHub Actions n8n to version 1.123.22.
- Update GitHub Actions n8n to version 2.9.3.
- Update GitHub Actions n8n to version 2.10.1.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| GitHub Actions | n8n | <= 1.123.22 | 1.123.22 |
| GitHub Actions | n8n | > 2.0.0 , <= 2.9.3 | 2.9.3 |
| GitHub Actions | n8n | > 2.10.0 , <= 2.10.1 | 2.10.1 |
| n8n | n8n | <= 1.123.22 | – |
| n8n | n8n | > 2.0.0 , <= 2.9.3 | – |
| n8n | n8n | > 2.10.0 , <= 2.10.1 | – |
Original title
n8n has a Sandbox Escape in its JavaScript Task Runner
Original description
## 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 `N8N_RUNNERS_ENABLED=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 (`N8N_RUNNERS_MODE=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](https://docs.n8n.io/hosting/configuration/task-runners/)
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 `N8N_RUNNERS_ENABLED=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 (`N8N_RUNNERS_MODE=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](https://docs.n8n.io/hosting/configuration/task-runners/)
nvd CVSS3.1
9.9
nvd CVSS4.0
9.4
Vulnerability type
CWE-94
Code Injection
- https://nvd.nist.gov/vuln/detail/CVE-2026-27495
- https://github.com/advisories/GHSA-jjpj-p2wh-qf23
- https://docs.n8n.io/hosting/configuration/task-runners Product
- https://github.com/n8n-io/n8n/releases/tag/[email protected] Release Notes
- https://github.com/n8n-io/n8n/releases/tag/[email protected] Release Notes
- https://github.com/n8n-io/n8n/releases/tag/[email protected] Release Notes
- https://github.com/n8n-io/n8n/security/advisories/GHSA-jjpj-p2wh-qf23 Vendor Advisory
Published: 25 Feb 2026 · Updated: 12 Mar 2026 · First seen: 6 Mar 2026