n8n security vulnerabilities: which version to run now
n8n fixed two batches of security flaws in three weeks, some of which let a workflow editor run code on the server. Check your version, update and harden.
If you run n8n on your own server, you have two rounds of security updates to install. On 28 October and again on 13 November, n8n published advisories for flaws in its workflow automation platform. The worst ones let anyone who can edit a workflow run code on the n8n host, and that host holds the credentials for every system your workflows touch. On 13 November the expression sandbox escape also got a CVE number, CVE-2026-126391, so vulnerability scanners will start flagging it this week.
What n8n fixed
Each advisory lists fixed versions for several release lines at once. These are the ones that matter most:
| Advisory | What it allows | Severity | Fixed in |
|---|---|---|---|
| Expression sandbox escape (CVE-2026-126391) | A user who can create or edit workflows runs code on the host | High (7.7) | 1.123.89, 2.45.5, 2.46.1, 3.0.1 |
| Deprecated Code nodes | Function, Function Item and LangChain Code nodes run code in the n8n main process | High (8.7) | 2.42.6, 2.43.3, 3.0.1 |
| GraphicsMagick in the Docker image | An untrusted image sent to the Edit Image node can lead to code execution | High (7.7) | 1.123.89, 2.45.5, 2.46.1, 3.0.1 |
| Owner account takeover | A custom role with user management rights can reset the owner’s password | High (7.5) | 2.47.6, 2.48.3, 3.2.2 |
| Unencoded IDs in integration nodes | Untrusted input, such as a webhook body, can steer a request to another API endpoint | Moderate | 1.123.96, 2.47.6, 2.48.3, 3.2.2 |
| Trigger credentials | A member who knows a credential ID can activate a trigger with someone else’s credential | Moderate | 1.123.96, 2.47.6, 2.48.3, 3.2.2 |
There are more moderate fixes on the advisories page, including an SSRF in the AWS Bedrock nodes. Most of these flaws need an n8n login. Two can also be reached from outside: the GraphicsMagick and integration node flaws, when a workflow passes input from a public webhook to the affected node. And the ones that need a login are still serious, because an n8n login is easier to get than it looks: a former colleague, a shared account, a contractor with editor rights, or a password that leaked somewhere else.
Why “authenticated” doesn’t mean “low risk” in n8n
An n8n instance is a key ring. It stores API keys and OAuth tokens for your CRM, mailbox, accounting package, database and AI providers. Code execution on the host means an attacker can read the encryption key and with it every stored credential. From there the problem is no longer n8n, but every system n8n can reach.
The integration node flaw is a different risk. It needs no malicious user at all, only a workflow that takes an ID from a public webhook and passes it to a node. A crafted value can then point the request at another endpoint of the same service, with the rights of your stored credential.
Which version should you run?
- 2.x: go to 2.48.3, or 2.47.6 if you stay on that minor version. Both include all fixes above.
- 3.x: go to 3.2.2 or later. n8n released 3.0 as a beta on 27 October and plans a stable 3.x for early December. Upgrading to 3.x is one-way: you can’t go back to 2.x afterwards.
- 1.x: 1.123.96 has the fixes that apply to 1.x, but n8n ends support for 1.x on 31 December 2026. There is no direct path from 1.x to 3.x, so plan the move to 2.x now. The deprecated Code nodes advisory lists no fix for 1.x at all.
Check what you run with docker exec <container> n8n --version, or look at the version in the
bottom left of the editor. In Docker, pin an exact image tag such as n8nio/n8n:2.48.3 instead of
latest, as n8n’s own update guide advises
for queue mode. That guide also asks you to update at least once a month.
What to do now
- Back up first. Export the database (or the
.n8nfolder with SQLite) and keep the encryption key somewhere safe. - Update to one of the versions above, on a test copy first if you have one.
- Replace the deprecated nodes. After the update, n8n blocks saving new or changed Function,
Function Item and LangChain Code nodes. Existing workflows keep running. Rewrite them with the
standard Code node, which runs in a separate task runner. Don’t set
N8N_DEPRECATED_NODES_BLOCK=false; that brings the hole back. - Review who can edit. List all users and roles. Remove accounts of people who left, and check custom roles for user management rights. Turn on two-factor authentication for the owner.
- Block nodes you don’t use with
NODES_EXCLUDE. The n8n docs suggest starting with Execute Command and Read/Write Files from Disk. Add Edit Image if no workflow needs it. - Check webhook workflows where public input ends up in an ID field of a node. Validate the value before it gets there.
- Run
n8n audit. The built-in audit reports unused credentials, risky nodes, unprotected webhooks and whether the instance is outdated.
If you think someone abused one of these flaws, updating isn’t enough. Rotate the credentials stored in n8n, starting with the ones that have the most rights. We described a similar cleanup in our article on the LiteLLM supply chain attack.
How we approach this
n8n is a good tool for connecting systems, and we use tools like it in process automation projects. What we add is the boring part: a pinned version with a monthly update slot, a separate service account per workflow with only the rights it needs, and no editor access for people who only need to see results. For a financial services client we put a separate API layer between the AI tools and the model providers, so keys sit in one place and every call is logged. The same idea works for n8n: the fewer secrets the automation server holds, the less a bug like this can expose.
Sources
- n8n security advisories, GitHub
- CVE-2026-126391: n8n before 1.123.89 RCE via workflow expression evaluation sandbox escape, CVE.org, published 13 November 2026
- Insufficient isolation in workflow expression evaluation (GHSA-gx3v-3x3v-f8r5), n8n, 28 October 2026
- Deprecated Code nodes allow code execution in the n8n main process (GHSA-9p7v-45m2-wxgj), n8n, 28 October 2026
- Insecure GraphicsMagick configuration (GHSA-f2cw-9483-7vcp), n8n, 28 October 2026
- Custom instance role with user management permissions gives control of the owner account (GHSA-q8rc-7m84-mfvj), n8n, 13 November 2026
- Integration nodes send authenticated requests to unintended API endpoints (GHSA-c772-hjfp-gfc2), n8n, 13 November 2026
- Workflow activation allows trigger nodes to use credentials the publisher cannot access (GHSA-h59h-rf6m-7jp5), n8n, 13 November 2026
- AWS Bedrock nodes skip SSRF protection for custom runtime endpoints (GHSA-g333-hr44-g82p), n8n, 13 November 2026
- Announcing n8n version 3.0, n8n community, 23 October 2026
- Updating n8n, n8n Docs
- Block specific nodes, n8n Docs
- Run security audits, n8n Docs