vm2: Host Promise rejection from an exposed constructor can terminate the vm2 host process

Why it is Yellow

• CVSS 6.8 medium
• On your watchlist: npm

Affected packages

References

• https://github.com/advisories/GHSA-2v2p-6j97-cjg9
• https://github.com/patriksimek/vm2/security/advisories/GHSA-2v2p-6j97-cjg9
• https://nvd.nist.gov/vuln/detail/CVE-2026-100722
• https://github.com/patriksimek/vm2/commit/6e487df9518e455e5e60faec3df3a0e2e27f9940
• https://github.com/patriksimek/vm2/releases/tag/v3.12.2
• https://www.vulncheck.com/advisories/vm2-before-3.12.2-host-process-termination-via-construct-trap
• https://github.com/advisories/GHSA-2v2p-6j97-cjg9

Original description

vm2 before 3.12.2 does not apply host-side Promise rejection handling in the sandbox-to-host construct trap. In BaseHandler, the apply trap calls markHostPromiseHandled() on the returned value, but the adjacent construct path returns the result of Reflect.construct without the same sanitization. If an embedder exposes a constructable host function whose constructor returns a native rejected Promise, an untrusted script executed via VM.run can invoke it with `new` and ignore the result; the rejected host Promise crosses the bridge unhandled and, under Node's strict unhandled-rejection policy, is promoted to an uncaught exception that terminates the host process.