Important n8n security update for self-hosted users

Sharing this because it matters if you run n8n on your own machine or server.

A critical security issue was disclosed in n8n. In plain English: if someone can access a vulnerable n8n instance (for example via a user account), they may be able to run code on the system behind it.

If you self-host n8n, check your version and update to a fixed release (the advisory lists the patched versions).

If you use n8n Cloud, this is handled through the Cloud update process, so you usually don’t need to do manual server work.

What to do:

Open n8n and check your version number.
If you’re behind the fixed versions listed in the advisory, update.
Updating should not erase your workflows, but making a backup before updates is always smart.

If you can’t update today:

Limit who can edit workflows and avoid exposing your instance publicly.

Advisory: https://cyberpress.org/n8n-automation-platform-vulnerability/

3 comments