Description
vm2 before 3.11.8 does not fully enforce the allowAsync: false option in VM and NodeVM. While localPromise.prototype.then is replaced with a handler that throws 'Async not available', the sandbox's Promise static methods (Promise.resolve, Promise.all, Promise.race, Promise.any, and Promise.allSettled) still assimilate attacker-supplied thenables: native promise resolution performs PromiseResolveThenableJob and invokes the sandboxed code's then method in a microtask without passing through the patched then, so the async restriction is never applied. As a result, sandboxed script can schedule work that runs after VM.run() or NodeVM.run() has returned and outside the configured timeout, continuing to execute after the host believes execution is complete.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| patriksimek | vm2 | < 3.11.8 | 3.11.8 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| npm | vm2 | < 3.11.8 | 3.11.8 | GHSA-f8gf-w286-fmq2 |
Advisories 1
- WID-SEC-2026-3071 vm2: Mehrere Schwachstellen BSI CERT-Bund (WID) · Oct 27, 2026
References
- GitHub Security Advisory (GHSA-f8gf-w286-fmq2) vendor-advisory
- VulnCheck Advisory: vm2 before 3.11.8 allowAsync Bypass via Promise Thenable third-party-advisory