SecPod

Learn Search

Search across all Learn content

← Back to Security Research
A Critical Vulnerability in vm2 Allows a Remote Attacker to Break Out of the Sandbox!

A Critical Vulnerability in vm2 Allows a Remote Attacker to Break Out of the Sandbox!

vm2 is a node module for creating a real sandbox in the node. It is also the most widely used Javascript sandbox library, which receives about 17.5 million downloads each month. A critical vulnerability(CVE-2022-36067) in vm2 can enable a remote attacker to escape the sandbox and execute arbitrary c...

Oct 11, 2022By Kavya K3 min read

vm2 is a node module for creating a real sandbox in the node. It is also the most widely used Javascript sandbox library, which receives about 17.5 million downloads each month. A critical vulnerability(CVE-2022-36067) in vm2 can enable a remote attacker to escape the sandbox and execute arbitrary code on the host. It offers a widely used software testing framework that may synchronously execute untrusted code in a single process. It is essential to have a patch management software to remediate this.

Due to its comprehensive control over the sandbox’s console output and the ability to restrict access to specific built-in modules or securely call methods and communicate data between sandboxes, it is one of the most liked testing environments used by millions of engineers.

Security researchers discovered a flaw in the vm2 sandbox when executing untrusted code. The sandbox configuration does not properly handle exceptions, leaving the system vulnerable to potential exploitation. This flaw allows an attacker to bypass the sandbox protections and gain access to the hypervisor host or the host executing the sandbox. A vulnerability management tool can prevent such attacks from occuring.

The vulnerability is assigned with CVE-2022-36067 and is rated critical (CVSS v3 score: 10). This vulnerability should alert all users of vm2 due to its potentially widespread impact.

“We were surprised when we discovered this vulnerability, as the vm2 sandbox module is extremely popular, and sandboxes, by their definition, should be safe. At the same time, we also felt glad that we found it, as we could then help secure it and give back to the community. After all, we are not only security Affected Product’s and enthusiasts but also developers who use open source components”

Dean Agron, CEO of Oxeye.

On August 28, the vm2 team released version 3.9.11, which addressed the SandBreak vulnerability. However, they have kept the technical details about the flaw hidden so far.

The root cause of the CVE-2022-36067 vulnerability, which Oxeye’s researchers have named SandBreak, resides in the way vm2 maintainers implemented a Node.js feature that allows them to customize the call stack of errors in the software testing framework.

Affected Products by CVE-2022-36067

  • vm2 Javascript sandbox library (npm) before 3.9.11.

Impact

A threat actor may bypass sandbox protections to obtain remote code execution privileges on the host running the sandbox.

Solution:

vm2 3.9.11 fixes the vulnerability for sandbox escape.

However, SanerNow Network Scanner detects this vulnerability. Finally, Use SanerNow and keep your systems updated and secure.

Featured Posts

Open WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels
WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

CVE Research

WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

Oct 1, 2026

Open OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure
OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

CVE Research

OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

Two critical vulnerabilities added to CISA KEV on September 24, 2026 reveal sharply different exploitation timelines. CVE-2026-71362 saw publicly documented exploitation roughly one day after Adobe's patch release, while CVE-2026-5430 had a 133-day vendor-remediation-to-observed-exploitation interval.

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026
Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

CVE Research

Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

Three Linux kernel vulnerabilities entered CISA’s KEV catalog on September 18, 2026, although their Linux 6.12 fixes were available 91–386 days earlier. This analysis separates patch availability, CVE publication, and known-exploitation status without treating KEV dates as first-attack dates.

Sep 28, 2026