CVE-2026-42231: n8n: Prototype Pollution in XML Webhook Body Parser Leads to RCE

Published Apr 29, 2026
·
Updated

Impact A flaw in the xml2js library used to parse XML request bodies in n8n's webhook handler allowed prototype pollution via a crafted XML payload. An authenticated user with permission to create or modify workflows could exploit this to pollute the JavaScript object prototype and, by chaining the pollution with the Git node's SSH operations, achieve remote code execution on the n8n host.

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.

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, a flaw in the xml2js library used to parse XML request bodies in n8n's webhook handler allowed prototype pollution via a crafted XML payload. An authenticated user with permission to create or modify workflows could exploit this to pollute the JavaScript object prototype and, by chaining the pollution with the Git node's SSH operations, achieve remote code execution on the n8n host. 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>=2.17.0<2.17.4
2.17.4
npm/n8n>=2.18.0<2.18.1
2.18.1
npm/n8n<1.123.32
1.123.32
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:30 PM
Data Sourced
via MITRE·06:30 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-42231?

CVE-2026-42231 is considered a moderate severity vulnerability, allowing for prototype pollution in the affected n8n versions.

2

How do I fix CVE-2026-42231?

To fix CVE-2026-42231, update n8n to version 2.17.4, 2.18.1, or a later version that includes the patch.

3

What versions of n8n are affected by CVE-2026-42231?

CVE-2026-42231 affects n8n versions between 2.17.0 and 2.17.4, as well as versions between 2.18.0 and 2.18.1, and all versions up to 1.123.32.

4

Who can exploit CVE-2026-42231?

An authenticated user with permissions to create or modify workflows can exploit CVE-2026-42231.

5

What is prototype pollution in the context of CVE-2026-42231?

In the context of CVE-2026-42231, prototype pollution refers to the ability to modify the JavaScript object prototype, which can lead to potential security risks or application disruption.

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