Description
vm2 is a sandbox library for running untrusted JavaScript in Node.js. In versions >= 3.10.0 and <= 3.11.7, Promises returned from the host realm into the sandbox are not marked as handled at the bridge boundary; only Promises created inside the sandbox are wrapped with a rejection-swallowing handler (lib/setup-sandbox.js), and the bridge only installs host-side rejection sanitizers when sandbox code calls .then/.catch/.finally. As a result, code running in the sandbox can invoke a host function that returns a rejected Promise (for example events.once() exposed via the NodeVM events builtin, or any embedder-provided Promise-returning API) and simply ignore the return value, leaving the host Promise unhandled so that Node.js's default unhandled-rejection behavior terminates the host process. This is an incomplete fix of GHSA-hw58-p9xv-2mjh. The issue is fixed in version 3.11.8.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| patriksimek | vm2 | 3.10.0 – < 3.11.8 | 3.11.8 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | vm2 | >= 3.10.0, < 3.11.8 | 3.11.8 | GHSA-gjq8-xm47-88rc |
Advisories 1
- WID-SEC-2026-3071 vm2: Mehrere Schwachstellen BSI CERT-Bund (WID) · Oct 27, 2026
References
- GitHub Security Advisory (GHSA-gjq8-xm47-88rc) vendor-advisory
- VulnCheck Advisory: vm2 3.10.0 through 3.11.5 Denial of Service via Host Promise third-party-advisory