Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Critical severity, with a CVSS score of 10, published 17 September 2026.
- Which products and versions are affected?
- vm2 (npm) = 3.11.6; Patrik Simek Vm2 3.11.6.
- Is there a fix for This vulnerability?
- A patch was published on 2026: Fixed in vm2 3.11.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run vm2 (npm) or Patrik Simek Vm2 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.
Technical details
The vulnerability is a sandbox escape in vm2's bridge gate (lib/bridge.js:1624) that sanitizes rejected host Promise values. The identity check only validates the direct call target, allowing attackers to use Function.prototype.call or .apply indirection to bypass sanitization. By invoking a rejection handler through p.then.call(p, undefined, cb) instead of direct p.then(undefined, cb), the intercepted target becomes Function.prototype.call rather than the original handler, preventing the sanitizer from running. An attacker can then access host objects exposed as Promise properties (e.g., err.detail.mainModule.require('child_process')) and execute arbitrary code.
Affected products
- Patrik Simek vm2 3.11.6
Timeline
- 2026-09-17: disclosed: Advisory published on GitHub Advisory Database
- 2026: patched: Fixed in vm2 3.11.7
- 2026-10-01: other: Advisory withdrawn as duplicate of GHSA-647f-g98j-qq25