CVE-2026-27577: n8n: Expression Sandbox Escape Leads to RCE
Impact 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.
Patches 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.
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. - 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.
Resources - Best practices for securing n8n - Initial vulnerability advisory: CVE-2025-68613
Other sources
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.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.10.1 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 2.9.3 - Upgrade
Upgrade
npm/n8nto a version that resolves this vulnerability.Fixed in 1.123.22 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.10.1Patch CVE-2025-68613 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 2.9.3Patch CVE-2025-68613 - Upgrade
Upgrade
n8nto a version that resolves this vulnerability.Fixed in 1.123.22Patch CVE-2025-68613 - Configuration
Limit workflow creation and editing permissions to fully trusted users only as a temporary mitigation if upgrading is not immediately possible.
n8n workflow_creation_and_editing_permissions = fully trusted users only - Compensating control
Deploy n8n in a hardened environment with restricted operating system privileges and network access to reduce impact of potential exploitation while upgrading is pending.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-27577?
CVE-2026-27577 has a high severity due to its potential for remote code execution (RCE).
How do I fix CVE-2026-27577?
To mitigate CVE-2026-27577, upgrade n8n to version 2.10.1, 2.9.3, or 1.123.22 depending on the version you are currently using.
What type of vulnerability is CVE-2026-27577?
CVE-2026-27577 is categorized as an expression sandbox escape vulnerability which can lead to remote code execution.
Who is affected by CVE-2026-27577?
CVE-2026-27577 affects users of n8n who have permissions to create or modify expressions.
Is there a patch available for CVE-2026-27577?
Yes, patches are available in the updated versions of n8n: 2.10.1, 2.9.3, and 1.123.22.