Critical · published January 27, 2026
🚨 A crafty n8n process exposes a critical RCE vulnerability that lets attackers run arbitrary code! 🔥 Think of it like a restaurant where the chef blindly follows any order that a diner yells from their seat — a recipe for disaster if someone decides to get creative with their requests! 🍽️ An authenticated attacker could take over the entire n8n instance, leading to full access to sensitive data, unauthorized modification of workflows, and the ability to execute system-level commands. This could result in an absolute compromise, putting everything at risk! Yikes! 🤯
Think of it like a restaurant where the chef blindly follows any order that a diner yells from their seat — a recipe for disaster if someone decides to get creative with their requests! 🍽️ This vulnerability arises from the insufficient isolation of expressions in n8n's workflow Expression evaluation system, allowing authenticated users to run malicious code in the context of the n8n process itself.
An authenticated attacker could take over the entire n8n instance, leading to full access to sensitive data, unauthorized modification of workflows, and the ability to execute system-level commands. This could result in an absolute compromise, putting everything at risk! Yikes! 🤯 Immediately update n8n to the latest version to patch this vulnerability. Review and limit user permissions to minimize the risk of exploitation. Consider auditing your workflows to ensure no malicious expressions are present. You've got this! By following these steps, you can secure your n8n instance and keep your workflows safe! 🛡️