Self-hosting n8n? Read this before your next workflow runs

If you self-host n8n on a VPS or cloud server, check your instance version today. On October 1, 2026, the n8n security team published an advisory bundle detailing 14 security vulnerabilities, including 10 high-severity flaws affecting credential isolation in shared workflows, OAuth persistence, and execution approval bypasses. While n8n Cloud instances received automatic patches, self-hosted instances remain exposed until you pull the latest Docker image. Below is what the advisory covers and how to update your server safely in under five minutes.

The most critical items involve credential boundary leaks: in multi-user setups, shared workflows containing sub-workflows or Agent Nodes could permit low-privilege editors to access credentials they were not authorized to view.

1. What the October 2026 security advisory found

The vulnerabilities, tracked across 14 GitHub Security Advisories (GHSAs), fall into four main categories:

1. Credential exposure in nested sub-workflows (GHSA-r6g9-5cpp-ppwr): In workspaces with multiple users, workflows invoking child sub-workflows or AI Agent nodes failed to enforce strict credential boundaries. A collaborator with view or edit rights on a parent workflow could extract API keys linked to sub-nodes.
2. Send-and-Wait approval bypass (GHSA-728h-pmr2-7cgh): A weakness in the HMAC validation mechanism for human-in-the-loop wait nodes allowed crafted requests to trigger executions without genuine human sign-off.
3. Unbounded OAuth client persistence (GHSA-3qcw-p65v-c7vq): Flaws on the authorize endpoint permitted unauthenticated persistence of OAuth client connections under specific configurations.
4. Expression injection in database nodes (GHSA-5qpp-pqww-h7fp): Certain database nodes permitted unescaped expression interpolation, risking arbitrary SQL command execution if supplied with untrusted input data.

Source: n8n Community: Security Advisory Roll-up

2. Which versions are safe?

To ensure your automations and connected credentials are fully protected, verify that your self-hosted instance is running at or above these build numbers:

• Version 2 line: Upgrade immediately to v2.41.4 or later.
• Version 1 legacy line: Upgrade to v1.123.83 or later.

If you are running any build between v2.0.0 and v2.41.3, your instance is vulnerable to the shared credential disclosure flaw if you have multiple editors on your team.

3. The 4-step Docker upgrade procedure

Upgrading a self-hosted Docker Compose installation does not destroy your workflows or database records as long as your volume mounts are mapped correctly. Follow this sequence:

1. 01

   Create an immediate database backup

   Export your SQLite database or dump your PostgreSQL database before executing image pulls: cp n8n_data/.n8n/database.sqlite backup.sqlite.

2. 02

   Update image tag in docker-compose.yml

   Edit your compose configuration to target image: n8nio/n8n:2.41.4 or set the tag to image: n8nio/n8n:latest.

3. 03

   Pull the patched container image

   Run docker compose pull to download the updated image layers from Docker Hub to your server.

4. 04

   Restart containers in detached mode

   Execute docker compose up -d to recreate the container. Check logs via docker compose logs -f to ensure migrations pass cleanly.

4. Should you move from self-hosting to n8n Cloud?

If your agency manages mission-critical client data but lacks dedicated DevOps monitoring, managing OS-level patches and database backups can become an operational burden.

• Self-hosted n8n: Best when you require strict local data residency under India's DPDP Act, want unlimited execution volume on a ₹800/month Hetzner or DigitalOcean VPS, or connect directly to internal SQL databases behind a firewall.
• n8n Cloud: Best when you want zero maintenance overhead, automated security patching, and managed uptime without managing Linux servers.

If your automations are handling client CRM syncs, billing webhooks, or voice agent call records, keeping your self-hosted infrastructure hardened is non-negotiable.

Book a call with Autopilot Studio for production n8n deployment and server hardening.