Security readout for executives and security teams
Plain-English summary
An n8n user who can create or edit workflows may abuse the Python Code node to break out of its sandbox. This can expose files from the n8n environment and, in some runner setups, lead to host compromise. The issue is fixed in listed n8n releases.
Executive priority
Prioritize patching if n8n is used for sensitive automation or if many users can edit workflows. The business risk is unauthorized file disclosure and possible system compromise from a legitimate but risky application permission.
Technical view
CVE-2026-27494 affects n8n before 1.123.22, 2.9.3, and 2.10.1. With Task Runners enabled, an authenticated low-privilege workflow editor can access insufficiently restricted Python built-ins from the Code node, enabling arbitrary file read and potentially RCE. Internal Task Runners create higher host-compromise risk than external Task Runners.
Likely exposure
Exposure is limited to n8n instances with N8N_RUNNERS_ENABLED=true where untrusted or semi-trusted users can create or modify workflows using the Code node. Internal Task Runner deployments carry the highest impact according to the advisory.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. Exploitation requires authentication and workflow creation or modification permission. No user interaction is required after the attacker has that access.
Researcher notes
Focus validation on permission boundaries, Task Runner mode, and Code node availability. The advisory states sandbox restrictions on Python built-ins were insufficient. Avoid assuming exposure where Task Runners are not enabled; the source specifically ties this issue to N8N_RUNNERS_ENABLED=true.
Mitigation direction
- Upgrade n8n to 1.123.22, 2.9.3, 2.10.1, or later.
- Restrict workflow creation and editing to fully trusted users.
- Temporarily disable the Code node using NODES_EXCLUDE with n8n-nodes-base.code.
- Treat workarounds as temporary; they do not fully remediate the vulnerability.
Validation and detection
- Inventory n8n versions and identify instances below fixed releases.
- Check whether N8N_RUNNERS_ENABLED is set to true.
- Review who can create or edit workflows.
- Determine whether internal or external Task Runners are used.
- Confirm whether the Code node is available or excluded.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-497: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-27494 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
7.1HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/n8n-io/n8n/security/advisories/GHSA-mmgg-m5j7-f83hCVE reference · x_refsource_CONFIRM
- https://github.com/n8n-io/n8n/releases/tag/n8n@1.123.22CVE reference · x_refsource_MISC
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.10.1CVE reference · x_refsource_MISC
- https://github.com/n8n-io/n8n/releases/tag/n8n@2.9.3CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive System Information to an Unauthorized Control Sphere
Exposure of Sensitive System Information to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.