Critical vulnerability in vm2 (CVE-2026-26956): breaks the sandbox and allows to run commands on the host with Node.js 25

A critical failure in the sandboxing library for Node.js vm2 - registered as CVE-2026-26956- allows malicious code to escape the cage and run arbitrary commands in the host. Vulnerability has been confirmed at least in version 3.10.4 and the maintainer published a concept test explosion, making finding it a practical threat to services that run third-party code in real time.

vm2 is widely used in learning platforms, online editors, automations and SaaS applications that accept and run user scripts, with more than 1.3 million downloads per week in npm. Fault mechanics is not a classic JavaScript permit bypass: the bookstore trusts JavaScript level protections - wrappers (Proxies) and object sanitation between contexts - but handling exceptions at WebAssembly level in V8 allows to intercept errors before these protections act. According to the official warning, the vector exploits the conversion symbol → chain to cause a specially built TypeError that makes an error object from the host's side "filtered" to the sandbox without being healed; from that corrupt instance the attackers can travel the chain of builders and reach interals likeprocess, opening the door to remote execution.

It is important to stress that the maintainer indicates that the problem has been replicated in environments where Node.js 25 (verified 25.6.1) when the exception management functions of WebAssembly and JSTag are activated. However, since vm2 has suffered from repeated sandbox escape vulnerabilities in recent years, the emergence of public exploits and the complexity of the V8 ecosystem increase the risk of additional discoveries or exploitation chains.

The practical consequences for organizations that depend on vm2 are clear: a remote operation can result in data exfiltration, access to memory or disk secrets, side movements from servers that run sandboxes, and also commitment of the integration pipeline if these environments process third-party code. The history of previous vulnerabilities in vm2 reinforces the need not to rely only on isolation controls implemented at the language level.

To mitigate the risk immediately and pragmatically, the direct recommendation is to update to vm2 version 3.10.5 or higher(the maintainer published the correction in the repository; see the technical notice in GitHub and the releases). If it is not possible to apply the patch immediately, evaluate disabling the functionalities of WebAssembly exception handling and JSTag in the affected environments, avoid running vm2 on Node.js 25 until confirming the secure configuration, or temporarily remove the code execution without reviewing. The maintainer's page contains both the advice with technical details like the release artifacts 3.10.5 that correct the failure.

Beyond the patch, it is appropriate to apply the principles of surface reduction and in-depth defense: run sandboxes in isolated processes with minimum operating system privileges, contain them with dedicated containers or VMs, apply strict network controls and egress policies, use resource control mechanisms (cgroups, CPU limits / memory) and minimize the exposure of secrets in the running environments. It is also recommended to implement detection and response to abnormal behaviors (system command execution, access to sensitive routes) and to rotate credentials that may have been accessible from compromised sandboxes.

For development and security equipment that manage dependencies, it is appropriate to audit where vm2 is used within repositories and pipelines, set versions in the package manager, add security checks in CI to detect and block vulnerable versions, and coordinate vulnerability tests including the published PoC analysis to understand the scope in your environment. Given the speed with which public exploits appeared, assuming a model of shared responsibility between maintainers and consumers is essential.

This incident highlights two lessons: first, that achieving robust isolation in JavaScript environments is complex and fragile when interacting with deeper layers of the running engine; and second, that organizations should not rely only on language-level sandboxing to run unreliable code. Maintaining up-to-date units, applying patches quickly and taking additional containment measures are actions that significantly reduce risk until the implementation architecture can be redone with stronger controls.