CVE-2026-27577: n8n: Expression Sandbox Escape Leads to RCE
n8n is an open source workflow automation platform. Prior to versions 2.10.1, 2.9.3, and 1.123.22, additional exploits in the expression evaluation of n8n have been identified and patched following CVE-2025-68613. An authenticated user with permission to create or modify workflows could abuse crafted expressions in workflow parameters to trigger unintended system command execution on the host running n8n. The issues have 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 all known vulnerabilities. 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 deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce the impact of potential exploitation. These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.
Security readout for executives and security teams
Plain-English summary
A low-privileged but authorized n8n workflow editor can use a malicious expression to run system commands on the n8n host. Successful abuse could expose data, alter workflows, disrupt service, and affect connected systems. The flaw is critical, but the supplied sources do not establish active exploitation.
Executive priority
Prioritize remediation immediately for affected deployments, especially those with multiple workflow editors or powerful host access. Require prompt version verification and upgrade ownership. Temporary permission and isolation controls are appropriate only while the upgrade is being completed. Escalate suspected command execution to incident response.
Technical view
CVE-2026-27577 is a CWE-94 expression-sandbox escape affecting n8n before 1.123.22, versions 2.0.0 through 2.9.2, and 2.10.0. Crafted expressions in workflow parameters can produce unintended host command execution without user interaction. The supplied CVSS 4.0 score is 9.4.
Likely exposure
Exposure exists where affected n8n versions allow authenticated users to create or modify workflows. Risk increases when those permissions extend beyond fully trusted users or the n8n host has broad operating-system privileges and network access. The bundle does not quantify deployment prevalence or identify specific exposed organizations.
Exploitation context
Exploitation requires authentication and workflow creation or editing permission; no victim interaction is required. Network reachability is reflected in the supplied CVSS vector. The bundle marks this CVE as absent from KEV and provides no cited evidence of active exploitation, public proof-of-concept availability, or observed attacks.
Researcher notes
This advisory describes additional expression-evaluation exploits identified after CVE-2025-68613. That history suggests earlier remediation alone may not cover these variants. The source bundle identifies two fixing commits, but it does not provide sufficient evidence here to characterize bypass mechanics, indicators, exploit reliability, or exploitation in the wild.
Mitigation direction
Upgrade to n8n 1.123.22, 2.9.3, 2.10.1, or a later applicable version.
Restrict workflow creation and editing to fully trusted users until upgrading.
Reduce the n8n host's operating-system privileges and network access.
Treat temporary restrictions as risk reduction, not complete remediation.
Validation and detection
Inventory every n8n deployment and record its exact installed version.
Confirm each deployment is on 1.123.22, 2.9.3, 2.10.1, or later.
Review which authenticated accounts can create or modify workflows.
Verify n8n runs with restricted host privileges and network access.
Review relevant workflow changes and host activity for unexpected command execution.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.