n8n CVE-2026-42232

Exploitation requires authenticated access to an n8n instance with workflow creation or modification permissions (CVSS PR:L confirms low-privilege authentication required). The attacker must specifically leverage the XML node component within a workflow, meaning the XML node must not be disabled via the NODES_EXCLUDE environment variable. The vulnerability exists in default configurations of affected n8n versions. Exploitation is limited to users who have been granted workflow editing capabilities through n8n's permission system-organizations that restrict workflow editing to a small number of administrators face significantly lower risk than those with broad workflow editing permissions. The scope change (S:C) in the CVSS vector indicates successful exploitation breaks out of workflow isolation to affect the entire n8n instance.

The CVSS vector AV:N/AC:L/PR:L/UI:N/S:C indicates network-accessible exploitation with low complexity requiring only low-privileged authentication, no user interaction, and critically includes scope change (S:C) meaning the vulnerability breaks out of its security boundary to impact other components. The 10.0 CVSS score is justified by the scope change combined with complete confidentiality, integrity, and availability impact. However, real-world risk is moderated by the PR:L requirement-attackers must first obtain authenticated access with workflow editing permissions, which in properly configured n8n instances should be restricted to trusted users. No CISA KEV listing exists, indicating no confirmed widespread or targeted exploitation. No public POC is referenced in available data. The authentication prerequisite significantly reduces attack surface compared to unauthenticated vulnerabilities, but the scope change and RCE capability make this critical for organizations where workflow editing permissions are broadly granted or where credential compromise is a concern. Organizations should prioritize patching based on their n8n permission model: critical priority if multiple users have workflow editing rights, high priority if tightly controlled.

An attacker with stolen or insider credentials possessing workflow editing permissions logs into the n8n instance and creates a malicious workflow containing an XML node. The attacker crafts specially formatted XML input that exploits the parsing vulnerability to inject malicious properties into JavaScript's Object.prototype, such as polluting properties used by execution contexts or command execution nodes. The attacker then chains this with other n8n nodes that reference the polluted prototype properties during workflow execution, triggering arbitrary code execution within the n8n server's Node.js runtime with the privileges of the n8n process, potentially accessing sensitive workflow data, credentials stored in n8n, or pivoting to other systems accessible from the n8n server.