vm2 is vulnerable to Sandbox Escape
100
Critical Risk
vm2's NodeVM uses a hard denylist of builtin modules that must not reach the sandbox even when the module allowlist is *. The denylist omits child_process, so guest code that requests it through *, an explicit entry, or the node: spelling gets the real host module. A single execSync call then runs arbitrary commands on the host, leading to a sandbox escape. The fix adds child_process to the dangerous builtins denylist so it is refused under the wildcard and on explicit request.
You are affected if you are using a version that falls within the vulnerable range and you run untrusted code in NodeVM with a builtin allowlist of * or named modules.
vm2 is vulnerable to Sandbox Escape in versions 3.11.0 - 3.12.0.
Upgrade the vm2 library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.