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
nvd · CVE-2026-92959
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-693
Original publisher date fields
published: 2026-09-17T14:18:02.130
lastModified: 2026-09-21T21:17:16.917
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON