Topic starter
11/06/2026 10:44 pm
TL;DR: A critical n8n flaw, CVE-2025-68613 with CVSS 9.9, lets authenticated workflow editors inject expressions that escape sandboxing and execute arbitrary code on the host, according to Orca Security. In practice, workflow automation platforms inherit host-level blast radius when expression evaluation is not tightly isolated, so patching and exposure review cannot wait.
Editorial analysis by NHI Mgmt Group, based on content published by Orca Security: “Critical n8n RCE vulnerability enables full server compromise”.
By the numbers:
- CVE-2025-68613 carries a CVSS score of 9.9/10.0, according to Orca Security.
Key questions
Q: What breaks when workflow expressions can escape sandboxing?
A: The workflow engine stops being a safe configuration layer and becomes a code execution surface.
Q: Why do authenticated workflow editors still create serious risk?
A: Authentication does not equal safety when the platform can execute code on the host.
Q: How should security teams prioritise remediation for exposed automation platforms?
A: Start with internet-facing or multi-tenant instances that process sensitive data or connect to privileged internal systems.
Practitioner guidance
- Patch vulnerable n8n instances immediately Upgrade self-hosted and embedded n8n deployments to 1.120.4, 1.121.1, or 1.122.0 and do not rely on earlier partial mitigations.
- Audit workflow editor access Review who can create or edit workflows, especially where interactive editing is enabled, and reduce that role to the smallest feasible population.
- Constrain the runtime process Run the automation engine with minimal host permissions, narrow filesystem access, and tightly scoped network and secret reach.
Bottom line: n8n expression injection shows how a trusted workflow editor can become a host execution path when sandboxing fails.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
12/06/2026 7:03 am
Workflow expression evaluation is a privileged execution boundary, not a configuration convenience. When an automation engine accepts user-supplied expressions, it is handling code-like input even if the product UI presents it as workflow editing. The governance mistake is to treat editor authentication as sufficient assurance. Practitioners should treat expression parsing and sandboxing as part of the host attack surface, because once that boundary fails the automation layer becomes an execution layer.
A question worth separating out:
Q: What does a workflow engine compromise mean for surrounding infrastructure?
A: It means the attacker may inherit the engine’s access to APIs, data, and downstream automation targets. Once arbitrary code runs on the host, the impact can extend well beyond the application into secrets exposure, workflow tampering, and lateral movement.
👉 Read our full editorial: n8n expression injection turns workflow editing into code execution