n8n-io n8n up to 1.123.31/2.17.3/2.18.0 prototype pollution

Summaryinfo

A vulnerability has been found in n8n-io n8n up to 1.123.31/2.17.3/2.18.0 and classified as critical. This issue affects some unknown processing. Performing a manipulation results in prototype pollution. This vulnerability is known as CVE-2026-42232. Remote exploitation of the attack is possible. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in n8n-io n8n up to 1.123.31/2.17.3/2.18.0. This affects an unknown part. The manipulation with an unknown input leads to a prototype pollution vulnerability. CWE is classifying the issue as CWE-1321. The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-42232 since 04/25/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059 according to MITRE ATT&CK.

Upgrading to version 1.123.32, 2.17.4 or 2.18.1 eliminates this vulnerability.

The vulnerability is also documented in the databases at EUVD (EUVD-2026-27104) and CERT Bund (WID-SEC-2026-1251). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Affected

• n8n n8n

Productinfo

Vendor

• n8n-io

Name

• n8n

Version

• 1.123.0
• 1.123.1
• 1.123.2
• 1.123.3
• 1.123.4
• 1.123.5
• 1.123.6
• 1.123.7
• 1.123.8
• 1.123.9
• 1.123.10
• 1.123.11
• 1.123.12
• 1.123.13
• 1.123.14
• 1.123.15
• 1.123.16
• 1.123.17
• 1.123.18
• 1.123.19
• 1.123.20
• 1.123.21
• 1.123.22
• 1.123.23
• 1.123.24
• 1.123.25
• 1.123.26
• 1.123.27
• 1.123.28
• 1.123.29
• 1.123.30
• 1.123.31
• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8
• 2.9
• 2.10
• 2.11
• 2.12
• 2.13
• 2.14
• 2.15
• 2.16
• 2.17
• 2.17.0
• 2.17.1
• 2.17.2
• 2.17.3
• 2.18.0

Website

• Product: https://github.com/n8n-io/n8n/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion