Quick answers
- Is CVE-2026-44791 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44791 being exploited in the wild.
- How severe is CVE-2026-44791?
- Critical severity, with a CVSS score of 9.9, published 23 June 2026.
- Which products and versions are affected?
- N8n < 1.123.43, >= 2.0.0-rc.0 < 2.20.7, >= 2.21.0 < 2.21.1, < 1.123.43, >= 2.0.0-rc.0 < 2.20.7, >= 2.21.0 < 2.22.1, < 1.123.43, >= 2.0.0-rc.0, < 2.20.7, >= 2.21.0, < 2.22.1; n8n (npm) SEMVER:introduced=0,fixed=1.123.43.
- Is there a fix for CVE-2026-44791?
- Yes. n8n (npm): upgrade to 1.123.43 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44791 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44791?
- Check whether you run N8n or n8n (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- n8n (npm): upgrade to 1.123.43 or later
npm install n8n@1.123.43
Technical details
A prototype pollution vulnerability (CWE-1321) exists in the n8n XML node due to an incomplete patch for a previous vulnerability. An authenticated attacker with permissions to create or modify workflows can exploit this by crafting malicious XML data that modifies the JavaScript object prototype. When combined with other nodes in a workflow, this can be escalated to Remote Code Execution (RCE) on the n8n host. The vulnerability is reachable over the network and requires low privileges. Patches are available in versions 1.123.43, 2.20.7, and 2.22.1.
Affected products
- n8n-io n8n < 1.123.43, >= 2.0.0-rc.0, < 2.20.7, >= 2.21.0, < 2.22.1
Identifiers
- CVE-2026-44791
- GHSA-wrwr-h859-xh2r
Timeline
- 2026-05-13: disclosed
- 2026-05-14: advisory