Loading vulnerability…
n8n Expression Sandbox Escape Remote Code Execution
CVE-2026-27577 is a critical expression sandbox escape vulnerability in n8n, an open source workflow automation platform. The flaw resides in the workflow expression evaluation mechanism, where crafted expressions in workflow parameters can bypass intended sandbox restrictions and reach unsafe runtime functionality. Public reporting attributes the issue to a missing case in the abstract syntax tree rewriter that allowed the Node.js process object to remain accessible instead of being safely transformed into the restricted expression context. An authenticated user with permission to create or modify workflows can abuse this weakness to trigger unintended system command execution on the host running n8n. The issue was identified as an additional exploit path related to earlier expression-evaluation weaknesses and was fixed in n8n versions 2.10.1, 2.9.3, and 1.123.22.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can result in remote code execution on the host running n8n with the privileges of the n8n process. This can enable full compromise of the application instance, execution of arbitrary operating system commands, access to sensitive application data, modification of workflows, and potential exposure of secrets available to the process environment. Reported downstream consequences include access to encryption material used by n8n and subsequent decryption of stored credentials, which may facilitate lateral movement to connected databases, cloud services, and internal systems.
If you can’t patch tonight, do this now.
If immediate upgrading is not possible, restrict workflow creation and editing permissions to fully trusted users only. Deploy n8n in a hardened environment with reduced operating system privileges and constrained network reachability to limit post-exploitation impact. These measures are only temporary risk-reduction steps and do not fully eliminate the vulnerability.
Patch, then assume compromise.
Upgrade n8n to a fixed release. The vulnerability is remediated in versions 2.10.1, 2.9.3, and 1.123.22; later versions that include these fixes should also be considered safe for this issue. Because this vulnerability affects the expression evaluation security boundary, remediation should prioritize vendor-provided patched builds rather than custom filtering or partial hardening alone.
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.