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.3, <= 3.11.6; Patriksimek Vm2 3.11.3 through 3.11.6.
- Is there a fix for This vulnerability?
- A patch was published on 2026-09-17: Version 3.11.7 fixes the issue 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.
Technical details
The builtin loader wraps host modules in read-only proxies, but method calls on EventEmitter objects like https.globalAgent are forwarded to the underlying host singleton. Sandboxed code can call agent.on('free', ...) to register a listener that fires whenever a pooled HTTPS connection is released, receiving the live TLSSocket and request options including authorization headers. An attacker with require('https') enabled in NodeVM configuration can steal credentials and eavesdrop on host traffic. The fix in version 3.11.7 isolates the agent per sandbox instance.
Affected products
- patriksimek vm2 3.11.3 through 3.11.6
Timeline
- 2026-08-24: disclosed
- 2026-09-17: advisory
- 2026-09-17: patched: Version 3.11.7 fixes the issue
- 2026-10-01: other: Duplicate advisory withdrawn