12 Critical Vulnerabilities Found in vm2 Node.js Library

Security researchers have disclosed a total of twelve vulnerabilities in vm2, a widely used open-source Node.js library, several of which carry the maximum possible CVSS score of 10.0. All affected versions up to and including 3.11.1 are impacted, and users are strongly urged to upgrade to the newly released version 3.11.2 immediately.

What Is vm2?

vm2 is a Node.js sandbox library designed to safely execute untrusted JavaScript code in an isolated environment, preventing that code from accessing the underlying host system. It is commonly used in platforms that need to run user-supplied or third-party scripts without exposing the server to risk. The discovery of these flaws fundamentally undermines that security guarantee.

What the Vulnerabilities Allow

All twelve flaws share a common and critical outcome: they enable sandbox escape, meaning an attacker can break out of the isolated environment and execute arbitrary code directly on the host machine. Several of the vulnerabilities also allow privilege escalation, prototype pollution, and the bypassing of built-in security allowlists, for example, loading restricted Node.js modules like child_process that would normally be blocked.

The flaws exploit a range of JavaScript internals, including the __lookupGetter__ method, the species property of Promise objects, the inspect function, SuppressedError, Symbol-to-string coercion, prototype chain manipulation via BaseHandler.getPrototypeOf, and weaknesses in the neutralizeArraySpeciesBatch() function, among others.

The most severe among them CVE-2026-43997, CVE-2026-44005, and CVE-2026-44006 all carry a perfect CVSS score of 10.0, while CVE-2026-43999 scores 9.9. The remaining flaws score between 9.1 and 9.8, placing every single one of the twelve in the critical severity range.

A Pattern of Bypass After Bypass

This latest batch of disclosures follows a critical sandbox escape flaw patched just a few months ago in January 2026. The vm2 maintainer, Patrik Simek, has previously acknowledged that the challenge of securely sandboxing JavaScript is ongoing, and that new bypasses are likely to continue emerging. Each patch has been followed by researchers finding new ways around the protections, a pattern that highlights the fundamental difficulty of enforcing strong isolation boundaries within the JavaScript runtime itself.

What to Do

Any application or service relying on vm2 to sandbox untrusted code should treat this as an urgent update. Upgrade to vm2 version 3.11.2 as soon as possible. Teams that cannot update immediately should consider disabling or restricting access to any functionality that relies on vm2 until the patch can be applied, given the critical severity of the vulnerabilities and the ease with which sandbox escapes can lead to full host compromise.

Resources

Comments

Popular posts from this blog

The Hidden Lag Killing Your SIEM Efficiency

Critical Vulnerability in Veeam Backup & Replication Exposes Enterprises to Remote Code Execution

Lotus Panda Hacks SE Asian Governments With Browser Stealers and Sideloaded Malware