Threat Intelligence Database

CVE-2026-47683 is a high-severity vulnerability in the open source Node.js sandbox vm2 prior to version 3.11.6. It involves insufficient enforcement of buffer allocation limits, allowing sandboxed code to bypass configured caps on memory allocation. This can lead to large synchronous external-memory allocations that may exhaust the host process. The issue is fixed in vm2 version 3.11.6.

CVE-2026-47686 is a critical vulnerability in the vm2 sandbox for Node.js prior to version 3.11.6. The vulnerability arises because the handleException() function does not sanitize the Error.cause property, allowing sandboxed code to access powerful host objects like process via specially crafted errors. This can lead to arbitrary command execution on the host. The issue is fixed in vm2 version 3.11.6.

CVE-2026-47698 is a critical vulnerability in the open source Node.js sandbox vm2 prior to version 3.11.6. The flaw allows sandboxed code to bypass prototype chain protections via stacked indirection through Function.prototype.call, enabling arbitrary host command execution. This is due to improper control of dynamically-managed code resources in specific vm2 modules. The issue is fixed in vm2 version 3.11.6.

The vm2 sandbox module has a vulnerability in its buffer allocation limit defense that can be bypassed using ArrayBuffer, SharedArrayBuffer, or TypedArray constructors. These constructors allocate host memory through the same underlying C++ path as Buffer.alloc but are not subject to the bufferAllocLimit cap. This allows an attacker to exhaust host memory synchronously, causing a denial of service by out-of-memory kills in constrained environments such as Docker, Kubernetes, or AWS Lambda. The vulnerability affects vm2 versions prior to 3.11.6 and all Node.js versions. A patch is available.

The vm2 NodeVM module with configuration builtin: ['*'] exposes the 'os' and 'dns' built-in modules, allowing sandboxed code to read sensitive host process information and perform process-wide state modifications. This includes reading host user info, network interfaces, and hostname, as well as hijacking DNS resolution via dns.setServers(). The vulnerability affects vm2 versions prior to 3.11.6 and has a critical CVSS score of 10. A patch is available to mitigate this issue by adding 'os' and 'dns' to the dangerous builtins list, preventing their exposure under the wildcard configuration.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM exposes some process-wide observability builtins when they are allowed through require.builtin. The diagnostics_channel, async_hooks, and perf_hooks builtins are not blocked by the dangerous builtin denylist. These modules are process-wide, not sandbox-local. Sandboxed code can use them to observe host application data across the vm2 boundary. This issue has been patched in version 3.11.4.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, a sandbox escape vulnerability in vm2 allows arbitrary code execution in the host process when untrusted code is executed with async support on runtimes exposing WebAssembly JSPI (WebAssembly.promising / WebAssembly.Suspending). In the tested configuration, a JSPI-backed Promise can reach Promise.prototype.finally() in a way that bypasses the expected Promise-species hardening and exposes a host-originated rejection object to attacker-controlled species logic, breaking the sandbox boundary. This issue has been patched in version 3.11.4.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.11.4.

vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM blocks several dangerous Node.js builtins such as module, worker_threads, cluster, vm, repl, and inspector. However, the denylist misses process and inspector/promises. Both can be used from sandboxed code to reach host-side execution primitives. This allows sandboxed code to bypass the intended builtin restrictions and execute code in the host process. This issue has been patched in version 3.11.4.

vm2 is a Node.js sandbox that prior to version 3.11.4 allowed sandboxed code to bypass network restrictions by accessing internal underscored HTTP modules. Although public network modules could be excluded, internal modules like _http_client and _http_server were not blocked, enabling outbound HTTP requests and listening sockets. This vulnerability is fixed in version 3.11.4.