Skip to content
Threat Feed
critical advisory

Multiple Vulnerabilities in vm2 Sandbox Library

The vm2 sandbox library is affected by multiple critical vulnerabilities, including remote code execution via sandbox escape, which allow attackers to manipulate data, disclose information, or execute arbitrary code.

CVE search metadata

CVE search record: CVE-2023-37480. Severity: low. CVSS: 2.7. EPSS: 0.69%. KEV: no. Product: vm2. Brief: Multiple Vulnerabilities in vm2 Sandbox Library. Brief link: https://feed.craftedsignal.io/briefs/2026-08-vm2-vulnerabilities/

CVE search record: CVE-2023-37367. Severity: medium. CVSS: 5.3. EPSS: 0.44%. KEV: no. Product: vm2. Brief: Multiple Vulnerabilities in vm2 Sandbox Library. Brief link: https://feed.craftedsignal.io/briefs/2026-08-vm2-vulnerabilities/

CVE search record: CVE-2023-36657. Severity: critical. CVSS: 9.8. EPSS: 0.57%. KEV: no. Product: vm2. Brief: Multiple Vulnerabilities in vm2 Sandbox Library. Brief link: https://feed.craftedsignal.io/briefs/2026-08-vm2-vulnerabilities/

What's new

  • 1. added coverage for vm2 Aug 17, 18:45 via ghsa

The vm2 sandbox library is subject to multiple critical vulnerabilities, tracked as CVE-2023-37480, CVE-2023-37367, and CVE-2023-36657. These vulnerabilities arise from flaws within the sandbox implementation that permit an attacker to escape the restricted environment. By bypassing the sandbox constraints, an unauthenticated attacker can execute arbitrary code on the host system, manipulate sensitive data, perform denial of service attacks, or disclose confidential information. Because vm2 is frequently used to execute untrusted JavaScript code in server-side environments, these vulnerabilities pose a significant risk to applications relying on this library for process isolation. Defenders should verify if their internal applications or third-party dependencies utilize vulnerable versions of vm2 and prioritize upgrading to secure versions or migrating to alternative sandboxing solutions.

Impact

Successful exploitation of these vulnerabilities leads to full sandbox escape, granting the attacker the ability to execute code with the privileges of the Node.js process. This may result in total system compromise, exfiltration of application secrets, and disruption of critical business services through denial of service. The scope of impact is widespread across any server-side application using the affected library versions for code evaluation.

Recommendation

  • Identify all applications within the environment utilizing the vm2 library via software composition analysis (SCA) or dependency auditing tools.
  • Patch or update affected applications to the latest secure version of vm2 immediately.
  • In environments where patching is not immediately feasible, evaluate the implementation of secondary security controls such as containerization or restricted service accounts to limit the blast radius of a potential sandbox escape.
  • Review application logs for unusual patterns or child process spawning initiated by the Node.js runtime environment associated with the vm2 library.

Immediate actions

Inventory applications using the vm2 library and prioritize patching

Application Security 48h

Mitigations

Upgrade vm2 to a patched version or replace library

immediate IT Operations

CVE-2023-37480, CVE-2023-37367, CVE-2023-36657