RetailboxMessage us

Is n8n Secure? A Self-Hosted n8n Security Checklist After the 2026 CVEs

By Mikhail Oskola, Founder & AI Automation Architect · · 11 min read

Checked: GitHub's advisory database for the n8n package (all severities, via the GitHub API), the advisories for the CVEs named in the table, n8n's docs on security audits, securing an instance, blocking nodes, updating self-hosted n8n and Cloud updates, and npm's release tags for n8n, all read on 18 November 2026.

n8n can be run securely, but a self-hosted instance won't update itself. Between December 2025 and May 2026, GitHub's advisory database recorded 24 critical vulnerabilities in n8n. At least two could be reached with no login at all, through a public webhook or form. Most of the rest needed a logged-in account, usually one allowed to edit workflows. So check two things first: which version you run, and who can edit. On 18 November 2026 the current stable release was 2.48.4, and the newest advisories were fixed in 2.38.2, 2.37.7 and 1.123.76. Then run n8n's built-in security audit. Facts checked against n8n's docs and GitHub's advisory database on 18 November 2026.

Is n8n secure? The short answer

n8n publishes each fix as a security advisory on GitHub, usually with the exact versions that close the hole. The weak spot is the gap between a fix shipping and your instance running it.

On n8n Cloud, that gap is n8n's problem. Its docs say it upgrades every Cloud instance at least every two weeks "so security fixes reach everyone", whichever update cadence the owner picks. The owner picks the release track and how often updates arrive, but the two-week minimum applies either way. Cloud is not untouched: the advisory for CVE-2026-21877 says plainly that "both self-hosted and n8n Cloud instances are impacted." The difference is who applies the fix.

On a self-hosted instance, you apply it. n8n's own update guide says to "try to update at least once a month", read the release notes for breaking changes, and test the update on a separate instance first. If nobody owns that job, the server keeps running whatever version it was installed with, and every advisory published since then applies to it.

The n8n vulnerabilities of 2025–2026, in plain words

Since 1 December 2025, GitHub's advisory database has listed 162 advisories for the n8n package: 24 critical, 60 high and 78 medium. The critical ones were published between 8 December 2025 and 14 May 2026. None has been rated critical since then, but 41 high-severity advisories came after May, the latest batch on 10 September 2026.

Most of the critical bugs let someone run their own code on the server n8n runs on. Once that happens, everything n8n can reach is exposed: the database, the files on the host and the API keys saved in your credentials.

Read the "login needed?" column carefully. Only two of these worked for a stranger on the internet, and both went through a public webhook or form. Most of the others needed an account that can create or edit workflows. On a small team that sounds safe until you count the former contractor who still has a login, or the shared account five people use.

n8n rated CVE-2026-27493 lower than its CVSS score (High rather than Critical), because it only works on a form built in an unusual way, and turning it into full control of the server takes a second bug. The table shows the advisory as GitHub lists it.

CVE (published)What it allowedLogin needed?Fixed in
CVE-2025-68613 (22 Dec 2025)Running code on the server through workflow expressionsYes, a user who can edit workflows1.120.4, 1.121.1
CVE-2026-21877 (6 Jan 2026)Running code on the server; Cloud was affected tooYes, a logged-in user1.121.3
CVE-2026-21858 (7 Jan 2026), CVSS 10.0Reading files on the server through certain form-based workflowsNo, through a public webhook or form1.121.0
CVE-2026-27493 (25 Feb 2026)Evaluating n8n expressions through submitted form data; with a second bug, running codeNo, but only on a form set up in an unusual way1.123.22, 2.9.3, 2.10.1
CVE-2026-33660 (25 Mar 2026)Reading local files and running code through the Merge node's SQL modeYes, a user who can edit workflows1.123.27, 2.13.3, 2.14.1
CVE-2026-44789 (14 May 2026)Corrupting n8n's internals through the HTTP Request node's pagination; combined with other techniques, running codeYes, a user who can edit workflows1.123.43, 2.20.7, 2.22.1

Which n8n version is safe to run today

There is no version that is safe for good, only versions with no known fix missing. On 18 November 2026, npm listed 2.48.4 as n8n's current stable release (published 13 November) and 2.49.0 as the beta. The newest advisories, from 10 September 2026, were fixed in 2.38.2, 2.37.7 and 1.123.76. Anything older than those is missing at least one published fix.

If you're still on version 1, read this before you relax. n8n still ships patches for the 1.123 line (1.123.97 came out on 16 November 2026), but two critical bugs in the Python Code node were only fixed in version 2: CVE-2025-68668 in 2.0.0 and CVE-2026-25115 in 2.4.8. Until you move to version 2, the advisories' own workarounds apply: switch Python off with N8N_PYTHON_ENABLED=false, or block the Code node entirely.

To see what you run, check the image tag in your Docker setup, or let the instance report in n8n's audit tell you (next section): it flags an outdated version. The full list of advisories, with fixed versions, is on n8n's GitHub page at github.com/n8n-io/n8n/security/advisories. Compare your version against it, not against a blog post, this one included.

Run n8n's own security audit first

n8n ships its own audit. There are three ways to start it: the command n8n audit on the server, a POST call to the /audit endpoint of the public API (you have to authenticate as the instance owner), or the n8n node inside a workflow, with Resource set to Audit and Operation to Generate.

It produces five risk reports. Credentials lists saved credentials that no workflow uses, or no recently active one. Those are keys sitting on the server for no reason, so delete what you don't need. Database flags expressions inside SQL query fields, the classic route to SQL injection when an expression carries outside input.

File system lists every node that touches files on the server. Nodes lists the official "risky" nodes in use (n8n's term for built-in nodes that can fetch and run code on the host), plus every community and custom node. Instance lists webhooks that anyone can call without credentials, missing security settings, and whether your version is outdated.

None of the reports is a verdict. A public webhook can be exactly what you want, for a website form for example. The point is that every item on the list should be there on purpose.

Self-hosted n8n security checklist

Run these after the audit, and again after any big change to who uses the instance. Most of them need the n8n admin screens and access to the server's environment variables, not a developer.

10 checks for a self-hosted n8n instance

  1. Check the version. Compare what you run with the newest fixed versions in n8n's GitHub advisories. Wrong if you're behind on your line, or still on version 1 with Python enabled in the Code node. Fix: update, after testing on a copy of the instance as n8n's update guide recommends.
  2. Go through every public webhook. The audit's Instance report lists webhooks with no authentication. Wrong if one exists that nobody can explain, or one that triggers something sensitive, like writing to the CRM or sending email. Fix: turn on authentication in the Webhook node, or switch off workflows nobody owns. For CVE-2026-21858, n8n's own temporary advice was to restrict or disable public webhook and form endpoints until you could update.
  3. Read your public forms. Open each workflow with a Form trigger or Form node. Wrong if a field shows the visitor's own input back and its text starts with an = sign, the setup CVE-2026-27493 needed. Fix: update, and remove the stray = sign.
  4. Count who can edit workflows. Open the user list. Wrong if someone who has left still has an account, if several people share one login, or if people who only need to see results can build workflows. Most of this year's critical bugs needed exactly that permission, and advisory after advisory gives the same first workaround: limit workflow creation and editing to fully trusted users. Fix: remove old accounts, give each person their own login, and turn on two-factor sign-in.
  5. Block nodes you don't use. The NODES_EXCLUDE environment variable stops n8n loading a node at all. n8n's docs suggest starting with Execute Command and Read/Write Files from Disk; Execute Command is blocked by default, so check nobody switched it back on. The advisories also name the Code, Merge, Git and HTTP Request nodes as temporary blocks while you can't update. Wrong if a node that can run commands on the server is enabled and no workflow needs it.
  6. Review community nodes. The Nodes report lists every community and custom node installed. Each one is code someone else wrote, running on your server. Wrong if you can't say who installed a node and what uses it. Fix: uninstall the ones nothing uses, and install new ones only from publishers you trust.
  7. Isolate the Code node. If workflows run JavaScript or Python, n8n's docs cover hardening task runners. The CVE-2026-25115 advisory says that in external mode a sandbox escape stays inside a separate sidecar container instead of the main n8n process. Fix: a developer moves task runners to external mode; the runner image version has to match the n8n version.
  8. Switch off the public API if you don't use it. Wrong if n8n's public REST API is enabled and nothing of yours calls it. Fix: disable it, as n8n's security docs describe. If you do use it, delete the API keys nobody uses.
  9. Limit where workflows can connect. n8n has an SSRF protection setting that controls which hosts and IP ranges workflow nodes can reach. Wrong if any workflow can send requests into your internal network or to the cloud provider's metadata address. Fix: turn the protection on and allow only the ranges your workflows need.
  10. Rotate secrets after a late update. If the instance ran a version with a known no-login bug while its webhooks or forms were public, assume the server's files were readable. Fix: rotate n8n's encryption key (n8n documents how) and replace the API keys and passwords saved in its credentials, starting with the ones that can spend money or send email.

Checked against n8n's documentation (security audit, securing overview, blocking nodes, updating) and the GitHub advisories named above on 18 November 2026. n8n moves fast: setting names can change between versions.

Credentials: where n8n keeps your API keys and what to rotate after a breach

n8n stores every credential you save (CRM tokens, email passwords, OpenAI keys) in its own database, encrypted with a key held on the server. n8n's update guide treats that encryption key and the database as one unit: a full backup includes both.

That matters after a breach. Several of this year's critical bugs let an attacker read files on the host or run code as the n8n process. Someone with that access may have both halves, the encrypted credentials and the key that opens them. Our reading, not n8n's: in that case, rotating n8n's encryption key is not enough on its own. The keys at Stripe, OpenAI or your CRM are the ones that can still be used, so replace those too.

Before anything goes wrong, make that rotation cheap. One key per integration, a spending limit wherever the provider offers one, and a list of where each key is used. Our vibe coding security checklist makes the same point about AI-built apps: what limits the damage is how much one key can spend and how fast you can replace it.

n8n vs Zapier vs Make: who patches what

Zapier and Make only run in the vendor's cloud, so patching their platforms is the vendor's job, the same as on n8n Cloud. Self-hosted n8n is the one option where it's yours. That's also why people choose it: control over data and running costs, with no per-task billing. You get the server, and its updates come with it.

If you're still deciding, our Make vs n8n vs Zapier comparison covers price and fit. For what the server itself costs next to n8n Cloud vs self-hosted plans, see our n8n pricing guide. If health data runs through your workflows, the n8n and HIPAA section covers which agreements you need on top of a secure server.

When to bring in help

You can run every check above yourself. Bring someone in when the instance runs workflows that touch money, customers or a CRM and nobody on the team has time to own the server, or when you've just found something in the audit and don't know how far it goes.

Whoever you pick, ask them who updates the server and how often, and where the encryption key is kept. Our guide on how to choose an n8n consultant lists the questions to ask before someone touches your n8n. If you'd rather hand the server over, that's our self-hosted n8n with support work.

If your workflows include AI steps that can send, write or delete, the server is only half of it. Our guide to AI agent security risks covers what an agent can be talked into, and our MCP security guide covers agents that get their tools over MCP.

Retailbox Automation runs security reviews of vibe-coded apps, AI agents and Zapier, Make and n8n automations. If you self-host n8n and you're not sure what the audit would find, tell us what your instance runs and which version it's on.

Sources

Frequently asked questions

Is n8n safe to self-host?+

Yes, if someone owns the updates. Between December 2025 and May 2026 GitHub recorded 24 critical n8n vulnerabilities, each fixed in a release. A self-hosted instance only gets those fixes when you update it, and n8n's own guide says to update at least once a month. Also limit who can edit workflows, put authentication on public webhooks, and run n8n audit.

Is n8n Cloud affected by the 2026 vulnerabilities?+

Some advisories affected Cloud too: the one for CVE-2026-21877 says both self-hosted and Cloud instances were impacted. The difference is who patches. n8n's docs say it upgrades every Cloud instance at least every two weeks so security fixes reach everyone, whatever update settings the owner chooses.

How do I check my n8n version?+

Look at the image tag your Docker setup runs, or run n8n's security audit: its Instance report flags an outdated version. Then compare your version with the fixed versions in n8n's security advisories on GitHub. On 18 November 2026 the newest advisories were fixed in 2.38.2, 2.37.7 and 1.123.76.

What does n8n audit check?+

It produces five reports. Credentials: saved credentials no workflow uses. Database: expressions in SQL query fields. File system: nodes that touch files on the server. Nodes: risky built-in nodes, community nodes and custom nodes. Instance: webhooks without authentication, missing security settings, and an outdated version. Run it with the n8n audit command, the /audit API endpoint or the n8n node.

Should I rotate credentials after updating n8n?+

If the instance ran a vulnerable version while its webhooks or forms were public, yes. Several 2026 bugs let attackers read files or run code on the server, which can expose both the encrypted credentials and the key that decrypts them. Rotate n8n's encryption key and replace the API keys stored in its credentials, starting with the ones that can spend money or send messages.

Who can review the security of my n8n, Zapier or Make workflows?+

Retailbox Automation runs security reviews of vibe-coded apps, AI agents and Zapier, Make and n8n automations. Whoever you hire, ask who updates the n8n server and how often, where the encryption key is kept, and which account each connection runs under.

Ready to automate?

30-minute free call. We'll find your highest-ROI automation — no obligation.