VM2 has been found to have a critical sandbox escape vulnerability This article explores vulnerability vm2 sandbox. . Sandbox isolation for running untrusted code is offered by this popular Node.js library.

Tracked as CVE-2026-22709 (GHSA-99p7-6v5w-7xg8), the flaw affects all versions up to and including 3.10.0 and has a maximum severity CVSS v3.1 base score of 10.0. Incomplete callback sanitization in Promise prototype handling is the cause of the vulnerability. The callbacks for localPromise.prototype.then were sanitized by the vm2 developers, but globalPromise.prototype.then was not sanitized. Attackers can get around sandbox restrictions and obtain code execution privileges on the underlying host system because async functions return global Promise objects instead of local ones.

Vulnerability of VM2 Sandbox An asymmetry in callback sanitization across promise chains is exploited by the vulnerability.

Researchers found Promise.prototype.Error stack manipulation can be used to manipulate catch callbacks. Versions Affected by the CVE ID Package Vulnerability Type Attack with CVSS Score Vector CVE-2026-22709 vm2 (npm) ≤ 3.10.0 10.0 Network for Sandbox Escape An attacker can access the Error constructor, which in turn permits arbitrary code execution via the Function constructor, by generating an error object with a symbolic name and initiating an async function. This progression is used by the attack chain to create a Function object with any payload code.

Through access to the child_process module, attackers have successfully carried out system commands like execSync() in proof-of-concept demonstrations, totally evading the sandbox isolation layer.

Learn more about the development of antivirus and malware software, network security mathematics, hacking, and cracking. To fix the issue, the maintainers of Computer Security Cloud Storage VM2 released version 3.10.2. This update effectively sanitizes The sandbox escape vector is closed by promise callbacks in both local and global prototype chains.

Businesses that use VM2 should update to version 3.10.2 or higher right away. Two days ago, Patrik Šimek, a co-founder of the package, released a GitHub advisory demonstrating active maintenance and a prompt resolution of the security issue. This should be a top priority for development teams that use VM2 for code sandboxing. Identify impacted deployments by conducting quick inventory assessments in both development and production environments.

Immediately deploy version 3.10.2 via your package management pipeline, and confirm that no production instances are still running vulnerable versions. Consider limiting VM2 execution contexts to trusted code only until patching is finished. For daily cybersecurity updates, check out LinkedIn and X.

To have your stories featured, get in touch with us.