The question
The client runs n8n to connect their CRM, inbox, and a couple of internal tools — a fairly typical setup for a small business that started automating with AI over the past year or two.
What we told them
Short answer: not about anything that already happened to them specifically, but yes, patch it today. The bug was a prototype-pollution flaw in one of n8n's built-in nodes, and it affected every self-hosted and cloud deployment running the vulnerable version — not something that singled them out. In plain terms, prototype pollution lets an attacker's input quietly reshape objects the application already trusts, which can end in the attacker running commands they were never supposed to be able to run. It had already been patched in a platform update by the time we talked.
The useful part of the conversation wasn't the CVE — it was what it revealed about a blind spot. Most businesses have a patching routine for laptops and servers. Almost none of them have one for the automation platform sitting in the middle of their stack, even though it usually holds the credentials for half a dozen other systems: the CRM, the inbox, sometimes finance tools. We walked them through three things:
- Check your version. If you're self-hosting n8n (or any workflow tool), confirm you're on a patched release — don't assume auto-updates caught it.
- Audit who can edit workflows. Credentials stored in an automation platform are often broader than anyone realizes — a compromised workflow editor account is effectively a master key to everything it touches.
- Put the platform on the same patch calendar as everything else. Not "we'll get to it" — a recurring check, same as you'd do for a server or a firewall.
Your automation platform is application software with its own vulnerabilities — patch it on the same schedule you patch your servers, not on a "we'll get to it eventually" schedule.