<?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>Cpe:2.3:a:vm2_project:vm2:*:*:*:*:*:node.js:*:* — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3avm2_projectvm2node.js/</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 21:16:46 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3avm2_projectvm2node.js/feed.xml" rel="self" type="application/rss+xml"/><item><title>VM2 Sandbox Breakout via Async Generator</title><link>https://feed.craftedsignal.io/briefs/2026-05-vm2-sandbox-breakout/</link><pubDate>Thu, 14 May 2026 21:16:46 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-vm2-sandbox-breakout/</guid><description>A sandbox breakout vulnerability exists in vm2, tracked as CVE-2026-45411, allowing attackers to execute arbitrary commands on the host system by manipulating async generators to catch host exceptions, leading to remote code execution.</description><content:encoded><![CDATA[<p>A critical sandbox breakout vulnerability has been identified in vm2, a popular Node.js sandbox environment. This flaw, identified as CVE-2026-45411, allows malicious code to escape the confines of the vm2 sandbox and execute arbitrary commands on the host system. The vulnerability stems from the improper handling of exceptions within async generators, specifically when using the <code>yield*</code> expression. This allows attackers to catch host exceptions and manipulate the execution flow to achieve code execution outside the sandbox. The affected versions are vm2 versions 3.11.2 and earlier. This vulnerability poses a significant risk to applications relying on vm2 for secure code execution, potentially leading to complete system compromise.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker provides malicious JavaScript code to the vm2 sandbox.</li>
<li>The malicious code defines an async generator function that utilizes the <code>yield*</code> expression.</li>
<li>The code triggers a host exception within the sandbox environment.</li>
<li>The exception is caught within the async generator using a specially crafted iterator.</li>
<li>The attacker manipulates the caught exception object to access host objects and functions.</li>
<li>This access is used to bypass the sandbox restrictions.</li>
<li>The attacker gains access to the <code>child_process</code> module.</li>
<li>The attacker executes arbitrary commands on the host system using <code>child_process.execSync()</code>.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows attackers to perform Remote Code Execution (RCE) on the host system. This can lead to a complete compromise of the affected system, including data theft, system corruption, and further propagation of malicious activity. Given the popularity of vm2 in sandboxing untrusted JavaScript code, a wide range of applications and systems could be at risk if they are using versions 3.11.2 or earlier.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade to vm2 version 3.11.3 or later to patch CVE-2026-45411.</li>
<li>Deploy the Sigma rule &ldquo;Detect VM2 Sandbox Breakout via Async Generator&rdquo; to your SIEM to detect potential exploitation attempts.</li>
<li>Implement strict input validation and sanitization to minimize the risk of malicious code being introduced into the vm2 sandbox.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>sandbox-escape</category><category>rce</category><category>vm2</category></item></channel></rss>