n8n: actively exploited code execution flaw, update self-hosted instances

In December 2025, n8n, the workflow automation tool many small businesses host themselves, published a critical advisory for CVE-2025-68613. A user who can log in and edit workflows could write an expression that escapes n8n's protections and runs commands on the server, with the same rights as n8n itself. That can mean full control of the instance and of the services it is connected to: email, CRM, accounting or payment tools.

The flaw is no longer theoretical. Akamai reported in February 2026 that a botnet called Zerobot was exploiting it, with attempts seen from mid-January 2026, to install malware. The US agency CISA added it to its catalogue of vulnerabilities exploited in the wild on March 11, 2026. Public exploit code exists.

An attacker needs an account, but that bar is lower than it sounds: shared logins, former staff or freelancers, weak passwords, or a second n8n flaw disclosed in January 2026 (CVE-2026-21858, see our separate alert) that researchers have chained with this one.

Who is affected

Self-hosted n8n from version 0.211.0 up to the fixed releases 1.120.4, 1.121.1 and 1.122.0. If you use n8n's hosted cloud service, check your version in the interface or ask n8n support.

How to check your site

Ask whoever set up your automations whether you run n8n, and where (a VPS, Docker, a hosting panel). The version number is shown in the n8n interface, or in the Docker image tag your developer uses.

What to do now

• Update n8n to the latest release, not only to the minimum fix. n8n published many more security fixes in 2026; for example, CVE-2026-25049, disclosed in February 2026, was fixed in 1.123.17 and 2.5.2.
• Until you can update, the advisory suggests limiting workflow creation and editing to fully trusted users, and running n8n with limited system rights and network access. These are short-term measures only.
• Review the user list and remove accounts nobody uses.
• If your instance was online and outdated in 2026, ask your developer to look for unknown workflows or processes and to rotate the credentials stored in n8n (API keys, email and database passwords).
• Instances updated since early 2026 are most likely protected against this flaw, but check the version.

This alert reports what the sources published and is not a guarantee about any specific site.