Skip to content
Blog

n8n Prototype Pollution & RCE Vulnerability (CVE-2026-42231) — High Severity

N8N-Banner-ucartz
In this article
  1. CVE Details
  2. Affected Products
  3. Current Status
  4. Severity Level
  5. Possible Solutions
  6. References

A significant security vulnerability has been identified in n8n, an open-source platform widely used for automating workflows. This flaw, tracked as CVE-2026-42231, could allow an authenticated attacker to execute malicious code remotely on affected n8n installations, posing a high risk to the platform's integrity and data security.

CVE Details

The vulnerability in n8n stems from a flaw in how the platform's webhook handler processes XML request bodies, specifically through its use of the xml2js library. This issue enabled what is known as 'prototype pollution.' In simple terms, an attacker with the ability to create or modify workflows could craft a special XML payload to manipulate the fundamental structure of JavaScript objects within n8n. By chaining this manipulation with the system's Git node's SSH operations, the attacker could ultimately achieve Remote Code Execution (RCE) on the n8n host server.

  • Product: n8n
  • Published Date: May 4, 2026
  • Severity: High
  • Status: Analyzed

Affected Products

This critical vulnerability impacts specific versions of the n8n workflow automation platform. Users running the enterprise version of n8n on Node.js are particularly affected if their installations have not been updated.

Specifically, the vulnerability exists in n8n versions prior to 1.123.32, 2.17.4, and 2.18.1.

Organizations utilizing these older versions are at risk and should prioritize updating their systems immediately.

Current Status

The vulnerability, identified as CVE-2026-42231, has been thoroughly analyzed and publicly disclosed. n8n developers have already released patches to address this flaw, making it crucial for users to apply the recommended updates.

Severity Level

CVE-2026-42231 is rated with a HIGH severity, carrying a CVSS score of 8.8. This high rating reflects the significant danger posed by the vulnerability. The ability for an authenticated user to achieve remote code execution means an attacker could gain full control over the affected n8n server, potentially leading to data breaches, system compromise, or further attacks on connected systems. Such an exploit requires an attacker to have prior authentication and permissions to create or modify workflows, but once these prerequisites are met, the impact can be severe.

Possible Solutions

The good news is that n8n developers have swiftly provided official patches to mitigate this vulnerability. To protect your n8n instances from CVE-2026-42231, it is strongly advised to upgrade to the patched versions:

  • n8n version 1.123.32 or later
  • n8n version 2.17.4 or later
  • n8n version 2.18.1 or later

Admins and developers should review their current n8n version and plan for an immediate upgrade to one of these secure releases. Regular updates are a cornerstone of maintaining a robust cybersecurity posture.

References

https://github.com/n8n-io/n8n/security/advisories/GHSA-q5f4-99jv-pgg5

Share
Alex Joseph

Alex Joseph

Alex Joseph is a Senior Support Staff professional with deep experience in server management, web hosting technologies, and cybersecurity operations. He works daily with Linux servers, cloud platforms, performance tuning, and security hardening, giving him strong real-world technical knowledge. Along with his support role, he write about security best practices, hosting infrastructure, and software management.

Related updates

Start Building Today

Ready to Get Started?

VPS, dedicated servers, streaming and managed hosting with 24/7 support from the Ucartz team.