CVE-2026-42232: n8n: XML Node Prototype Pollution to RCE

Published Apr 29, 2026
·
Updated

Impact An authenticated user with permission to create or modify workflows could achieve global prototype pollution via the XML Node leading to RCE when combined with other nodes exploiting the prototype pollution.

Patches The issue has been fixed in n8n versions 1.123.32, 2.17.4, and 2.18.1. Users should upgrade to one of these versions or later to remediate the vulnerability.

Workarounds If upgrading is not immediately possible, administrators should consider the following temporary mitigations: - Limit workflow creation and editing permissions to fully trusted users only. - Disable the XML node by adding n8n-nodes-base.xml to the NODESEXCLUDE environment variable.

These workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.

Other sources

n8n is an open source workflow automation platform. Prior to versions 1.123.32, 2.17.4, and 2.18.1, an authenticated user with permission to create or modify workflows could achieve global prototype pollution via the XML Node leading to RCE when combined with other nodes exploiting the prototype pollution. This issue has been patched in versions 1.123.32, 2.17.4, and 2.18.1.

MITRE

Affected Software

6 affected componentsFixes available
npm/n8n<1.123.32
1.123.32
npm/n8n>=2.17.0<2.17.4
2.17.4
npm/n8n>=2.18.0<2.18.1
2.18.1
n8n N8n Node.js<1.123.32
n8n N8n Node.js>=2.17.0<2.17.4
n8n N8n Node.js=2.18.0

Event History

Apr 29, 2026
Advisory Published
via GitHub·09:25 PM
Data Sourced
via GitHub·09:25 PM
DescriptionSeverityWeaknessAffected Software
May 4, 2026
CVE Published
via MITRE·06:34 PM
Data Sourced
via MITRE·06:34 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-42232?

CVE-2026-42232 is considered a critical vulnerability due to its potential for remote code execution through global prototype pollution.

2

How do I fix CVE-2026-42232?

To remediate CVE-2026-42232, upgrade n8n to versions 1.123.32, 2.17.4, or 2.18.1.

3

Who is affected by CVE-2026-42232?

CVE-2026-42232 affects authenticated users of n8n who have permissions to create or modify workflows.

4

What are the implications of CVE-2026-42232?

The implications of CVE-2026-42232 include the potential for an attacker to exploit prototype pollution to execute arbitrary code.

5

Is there a workaround for CVE-2026-42232?

Currently, the best practice is to upgrade to the patched versions as there are no known workarounds for CVE-2026-42232.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203