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.7; Patriksimek Vm2 <= 3.11.7.
- Is there a fix for This vulnerability?
- Yes: fixed in 3.11.8. 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 Patriksimek 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.
How to fix
- Fixed in: 3.11.8
Technical details
The vulnerability is a sandbox escape in NodeVM (part of vm2) that allows attackers to access the host __proto__ getter/setter through console._stdout and console._stderr properties. By overwriting EventEmitter.prototype.emit and triggering process events, attackers can execute code with process context, bypassing code generation restrictions. This requires the attacker to have code execution within the vm2 sandbox, but escapes isolation entirely.
Affected products
- Patriksimek vm2 <= 3.11.7
Timeline
- 2026-09-17: disclosed
- 2026-10-05: advisory: Advisory withdrawn as duplicate of GHSA-88hf-g992-jg85