External risk intelligence

vm2 sandbox escape lets attackers run any code on your system

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-44008

A critical security flaw in the Node.js vm2 sandbox allows attackers to escape and run any code on your system, potentially exposing sensitive operations. Update vm2 immediately.

4Halo Surface Signal

Vm2 Project Vm2

before 3.11.2

External exposure likelihood

Halo Surface Signal score for CVE-2026-44008

The vm2 library is specifically designed to execute untrusted code in a sandboxed environment. This library is commonly integrated into internet-facing web applications, APIs, and online code execution platforms that accept and run dynamic input from end-users, making the vulnerable component a direct part of the public-facing attack surface in these deployments.

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in vm2, a Node.js sandbox, that allows code to break out of the sandbox and run commands on the host system. This issue could expose sensitive operations to unauthorized execution if not addressed.

  • Enables arbitrary code execution.
  • Affects systems running untrusted code.
  • Allows escape from the sandbox.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability to break out of the `vm2` sandbox and execute arbitrary code on the host system. This is achieved by manipulating array prototypes within the sandbox to expose host objects, specifically the host `Function` object. This allows for command execution by leveraging a flaw in how the `neutralizeArraySpeciesBatch` method interacts between the sandbox and the host environment.

  • No authentication required.
  • Vulnerable code execution.
  • Escapes sandbox environment.

Live Threat

Current exploitation, exposure, and threat context

Attackers are likely to weaponize this vulnerability because it offers a straightforward path to escaping the Node.js vm2 sandbox and executing arbitrary code on the host system. This type of critical sandbox escape is highly desirable for attackers aiming to gain control over vulnerable systems.

  • Public exploit available.
  • Remote code execution capability.
  • Affects widely used sandbox.

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize updating vm2 to version 3.11.2 or later immediately due to the critical severity and potential for arbitrary code execution. If patching is not feasible, isolate affected services from the network to prevent exploitation.

  • Update vm2 to 3.11.2 or newer.
  • Isolate services if patching is delayed.
  • Monitor for suspicious outbound connections.

Frequently asked questions

What is vm2 and why is it used?

vm2 is an open-source sandbox designed for Node.js applications. It is used to safely execute untrusted code by isolating it from the main system, preventing potential harm or unauthorized access.

How does CVE-2026-44008 allow attackers to escape the sandbox?

This vulnerability, a CWE-668 (Exposure of Resource to Incorrect Control Sphere), allows attackers to manipulate array prototypes within the sandbox. This manipulation can expose host objects, like the Function object, enabling code to break out of the isolated environment and execute on the host system.

What are the preconditions for an attacker to exploit this vulnerability?

An attacker does not need any special privileges or authentication to exploit this vulnerability. The vulnerability is triggered by running specific code within the vulnerable vm2 sandbox that manipulates array prototypes.

Who should be concerned about this vulnerability based on its exposure?

Organizations with internet-facing applications or services that execute dynamic user-submitted code, such as online code editors or platforms, should be particularly concerned. This is because the vulnerable vm2 component is likely part of their public-facing attack surface.

What is the immediate first step for running affected technology?

The most critical first step is to update vm2 to version 3.11.2 or a later version immediately. If an immediate update is not possible, isolating the affected services from the network can help mitigate the risk of exploitation.

References