Quick answers
- Is CVE-2026-92944 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92944 being exploited in the wild.
- How severe is CVE-2026-92944?
- Critical severity, with a CVSS score of 9.8, published 17 September 2026.
- Which products and versions are affected?
- vm2 (npm) >= 3.10.2, <= 3.11.6, SEMVER:introduced=3.10.2,fixed=3.11.7.
- Is there a fix for CVE-2026-92944?
- Yes. vm2 (npm): upgrade to 3.11.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92944 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92944?
- Check whether you run vm2 (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- vm2 (npm): upgrade to 3.11.7 or later
npm install vm2@3.11.7
Technical details
The vulnerability is a sandbox escape affecting vm2 versions 3.10.2 through 3.11.6 on Node.js 26. It exploits a stale PromiseThenLookupChain protector in V8 14.6 where Promise.prototype.finally() bypasses vm2's wrapper protections. An attacker can craft an async function that returns a Promise with an attacker-controlled constructor Symbol.species property, allowing them to reach the host Function constructor and process object, thereby executing arbitrary code outside the sandbox. The attack requires only the ability to execute code within the vm2 sandbox context. Patches should be available in later versions of vm2.
Affected products
- vm2 vm2 3.10.2 through 3.11.6
Identifiers
- CVE-2026-92944
- GHSA-27g9-p43v-cw3v
Timeline
- 2026-09-17: disclosed