CVE-2026-44789 is a critical prototype pollution flaw (CVSS 9.9 in the record) in the n8n HTTP Request node. A user who can edit workflows could corrupt global objects, and with other techniques reach remote code execution. Upgrade to 1.123.43, 2.20.7 or 2.22.1, depending on your branch.
What's affected
From the project advisory for the n8n npm package:
- Affected: versions 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. In many teams that is a wide group, so treat workflow editors as part of the trust boundary.
Two other n8n issues were fixed in the same releases: CVE-2026-44791 in the XML node, and CVE-2026-44792 in Source Control pull. One upgrade covers all three.
How to check if you're exposed
Check the version you run:
npm ls n8n
docker inspect --format '{{.Config.Image}}' <container-name>
You can also see the version in the n8n interface under the help menu. Then list who can create or edit workflows, and whether any of those people are outside the team that owns the instance.
What to do now
- Upgrade n8n to 1.123.43, 2.20.7 or 2.22.1 or later.
- As a short term step, limit workflow creation and editing to fully trusted users. The advisory notes this does not fully fix the risk.
- You can also exclude the HTTP Request node by adding
n8n-nodes-base.httpRequestto theNODES_EXCLUDEenvironment variable, which stops it from being used until you upgrade. This will break workflows that use the node. - Review recent workflow changes for nodes or settings you do not recognize.
Why it matters
The class is CWE-1321 (improperly controlled modification of object prototype attributes). In JavaScript, objects inherit from a shared prototype. If code copies a key into an object without blocking special names, a user can change that shared prototype, and every object in the process then picks up the change.
On its own, this can break logic or crash the process. As the advisory says, it can lead to code execution when combined with other techniques, because other code may read the polluted values as trusted settings. Workflow platforms are exposed to this class because they let users supply structure and parameters.
The record does not mark this CVE as KEV, and the advisory does not report exploitation.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Do I need all three n8n CVEs patched separately?
No. The three advisories name the same fixed versions, so one upgrade covers them.
Is disabling the node a real fix?
No. The advisory calls it a short term measure that does not fully remediate the risk.
Sources
Last reviewed: 19 October 2026.
