Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

n8n XML Node Prototype Pollution Leading to RCE

IdentifiersCVE-2026-42232CWE-1321· Improperly Controlled Modification…

CVE-2026-42232 is a vulnerability in n8n, the open source workflow automation platform. In n8n versions prior to 1.123.32, 2.17.4, and 2.18.1, an authenticated user with permission to create or modify workflows can trigger global prototype pollution through the XML Node. The flaw allows attacker-controlled properties to be introduced into the global prototype chain during workflow creation or modification. On its own, this corrupts application object behavior globally; when chained with other workflow nodes that consume or act on polluted prototype properties, the condition can be escalated to remote code execution. The issue is specifically described as originating in the XML Node component and affecting users with low privileges sufficient to edit workflows.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated workflow editor to poison the global prototype chain within n8n. This can alter application-wide object behavior and, when combined with other susceptible nodes, lead to remote code execution. The resulting impact is high across confidentiality, integrity, and availability, as an attacker may execute arbitrary code in the context of the n8n deployment, tamper with workflows or data, and disrupt service operation.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict workflow creation and modification permissions to fully trusted users only. Additionally, disable the XML Node by adding n8n-nodes-base.xml to the NODES_EXCLUDE environment variable. These measures reduce exposure but are temporary mitigations and do not fully eliminate the underlying risk.

Remediation

Patch, then assume compromise.

Upgrade n8n to a fixed release. The vulnerability is patched in versions 1.123.32, 2.17.4, and 2.18.1. Deploy the appropriate fixed version for the branch in use, or any later release that includes the patch.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
N8nN8napplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.