Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.1
n8n: Untrusted Users Can Read Sensitive Files
CVE-2026-27494
GHSA-mmgg-m5j7-f83h
Summary
An authenticated user with edit permissions can access and read sensitive files on the n8n server, potentially leading to full server compromise. To fix this, update to version 2.10.1 or later. If updating isn't possible, limit user permissions and temporarily disable the Code node.
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 Arbitrary File Read via Python Code Node Sandbox Escape
Original description
## 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 `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 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 `NODES_EXCLUDE` environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
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`.
## 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 `NODES_EXCLUDE` environment variable.
These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
nvd CVSS3.1
9.9
nvd CVSS4.0
7.1
Vulnerability type
CWE-497
- https://nvd.nist.gov/vuln/detail/CVE-2026-27494
- https://github.com/advisories/GHSA-mmgg-m5j7-f83h
- https://github.com/n8n-io/n8n/releases/tag/[email protected] Product
- https://github.com/n8n-io/n8n/releases/tag/[email protected] Product
- https://github.com/n8n-io/n8n/releases/tag/[email protected] Product
- https://github.com/n8n-io/n8n/security/advisories/GHSA-mmgg-m5j7-f83h Vendor Advisory Mitigation
Published: 25 Feb 2026 · Updated: 12 Mar 2026 · First seen: 6 Mar 2026