Node.js default behavior for unhandled rejections is to terminate the process, allowing an attacker to crash the entire application host. This vulnerability is particularly critical for multi-tenant environments, notebook workers, or plugin hosts that expose async host APIs or allow the 'events' builtin in NodeVM. This is a regression of hardening efforts originally introduced in GHSA-hw58-p9xv-2mjh and persists across major Node.js versions, including v16, v18, v20, v22, v24, and v25.

Attack Chain

1. Attacker gains the ability to execute arbitrary code within a vm2 sandbox environment.
2. Attacker identifies an exposed host-realm function (e.g., via sandbox configuration) that returns a Promise.
3. Attacker invokes the host function to obtain a host-realm Promise instance.
4. Alternatively, in NodeVM configurations, the attacker utilizes the events builtin to call events.once().
5. Attacker triggers a rejection on the host-side object or event emitter.
6. The bridge returns the rejected Promise to the sandbox without attaching a defensive .catch() or rejection handler.
7. Attacker ignores the returned value, leaving the host Promise unhandled.
8. The host Node.js runtime detects the unhandled rejection and terminates the parent process, causing a DoS.

Impact

Successful exploitation results in the immediate termination of the host Node.js process. This impacts any multi-tenant system, web service, or background worker utilizing vm2 for code isolation. Because the payload can be replayed after a process restart, automated recovery policies are ineffective against this primitive.

Recommendation

Immediate mitigation is required for all applications using vm2.

• Implement a process-level unhandledRejection handler in the host Node.js application to catch and swallow rejections originating from the vm2 sandbox, preventing process termination.
• Audit all NodeVM configurations; disable the events builtin if it is not strictly required for sandbox functionality.
• Restrict the exposure of host-realm functions that return Promises to sandboxed environments.
• Monitor logs for the node:internal/process/promises uncaught exception errors to identify potential exploitation attempts.