<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>CVE-2026-44791 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-44791/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 14 May 2026 16:22:47 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-44791/feed.xml" rel="self" type="application/rss+xml"/><item><title>n8n XML Node Prototype Pollution Patch Bypass Leads to RCE</title><link>https://feed.craftedsignal.io/briefs/2026-05-n8n-xml-prototype-bypass/</link><pubDate>Thu, 14 May 2026 16:22:47 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-n8n-xml-prototype-bypass/</guid><description>An authenticated n8n user with workflow creation privileges can bypass a previous patch for XML node prototype pollution, potentially leading to remote code execution on the n8n host when combined with other nodes; patched in versions 1.123.43, 2.20.7, and 2.22.1.</description><content:encoded><![CDATA[<p>An authenticated user with permission to create or modify workflows can bypass the patch for GHSA-hqr4-h3xv-9m3r in the XML node of n8n, a workflow automation platform. This vulnerability, identified as CVE-2026-44791, allows for prototype pollution. Successful exploitation, when chained with other nodes, can lead to remote code execution (RCE) on the n8n host. The affected versions include n8n versions prior to 1.123.43, versions 2.21.0 to 2.22.1 (excluding 2.22.1), and versions 2.0.0-rc.0 to 2.20.7 (excluding 2.20.7). This vulnerability matters to defenders because it allows attackers to gain complete control over the n8n instance, potentially compromising sensitive data and enabling further malicious activities.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker gains authenticated access to an n8n instance with workflow creation and modification privileges.</li>
<li>The attacker crafts a malicious workflow that includes the XML node.</li>
<li>The attacker exploits CVE-2026-44791, bypassing the patch for GHSA-hqr4-h3xv-9m3r by manipulating XML node parameters to inject a prototype pollution payload.</li>
<li>The prototype pollution modifies JavaScript object prototypes within the n8n environment.</li>
<li>The attacker chains the XML node with other nodes in the workflow (e.g., Function node, Execute Command node).</li>
<li>The polluted prototypes are leveraged by the subsequent nodes to execute arbitrary JavaScript code.</li>
<li>The arbitrary code execution allows the attacker to execute system commands on the n8n host.</li>
<li>The attacker achieves remote code execution (RCE), gaining control of the n8n host and potentially compromising the underlying system.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-44791 allows an attacker to achieve remote code execution on the n8n host. This could lead to the complete compromise of the n8n instance, potentially affecting all workflows and data managed by the platform. The attacker could potentially access sensitive information, modify workflows for malicious purposes, or use the compromised host as a pivot point for further attacks within the network. The vulnerability affects n8n instances running vulnerable versions prior to the patched versions, impacting any organization using n8n for workflow automation.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade n8n to version 1.123.43, 2.20.7, or 2.22.1 or later to remediate CVE-2026-44791, as mentioned in the overview.</li>
<li>Deploy the Sigma rule &ldquo;Detect n8n XML Node Prototype Pollution Attempt&rdquo; to identify suspicious workflow creations involving the XML node, as described in the rules section.</li>
<li>If immediate upgrade is not possible, implement the suggested workarounds by limiting workflow creation/editing permissions or disabling the XML node via the <code>NODES_EXCLUDE</code> environment variable, as detailed in the overview section.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>prototype pollution</category><category>RCE</category><category>n8n</category><category>CVE-2026-44791</category></item></channel></rss>