vm2 before 3.11.8 does not fully enforce the allowAsync: false option in VM and NodeVM. While…
Historical advisory recorded 25 Oct 2026 16:19:28 UTC. Read the latest advisory.
nvd · CVE-2026-92959
Publishedvm2 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-92959 · CVE overview and exploitation status
nvd · CVE-2026-92959
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.