CVE-2026-44791 is a critical prototype pollution patch bypass (CVSS 9.9 in the record) in the n8n XML node. A user who can edit workflows could bypass an earlier fix and, with other nodes, reach code execution on the host. Upgrade to 1.123.43, 2.20.7 or 2.22.1.
What's affected
From the project advisory for the n8n npm package:
- Affected: before 1.123.43, before 2.20.7, and before 2.22.1.
- Fixed: 1.123.43, 2.20.7 and 2.22.1 or later.
The attacker needs permission to create or modify workflows. The same release fixes CVE-2026-44789 and CVE-2026-44792.
How to check if you're exposed
Check your n8n version:
npm ls n8n
docker inspect --format '{{.Config.Image}}' <container-name>
Then list who can create or edit workflows. Treat each of them as someone who can run code on the host until you are patched.
What to do now
- Upgrade n8n to 1.123.43, 2.20.7 or 2.22.1 or later.
- Limit workflow editing to trusted users in the meantime.
- If you cannot upgrade, the advisory suggests excluding the XML node by adding
n8n-nodes-base.xmlto theNODES_EXCLUDEenvironment variable. Workflows that use the node will stop working. - Review recent workflow edits for changes you do not recognize.
Why it matters
The class is CWE-1321 (improperly controlled modification of object prototype attributes). A patch bypass means the first fix handled one way to reach the bug and missed another. When a project fixes a class of flaw by blocking a pattern, it is worth checking that the shared root cause is addressed too.
Workflow tools let users run logic on the server, so permission to edit workflows is close to permission to run code. The record does not mark this CVE as KEV.
Quick check
Which earlier fix was bypassed?
The record names CVE-2026-42232 for the XML node. The advisory refers to its own earlier advisory identifier.
Sources
Last reviewed: 19 October 2026.
