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 9.9, published 17 September 2026.
- Which products and versions are affected?
- vm2 (npm) >= 3.11.3, <= 3.11.6; Vm2 3.11.3 through 3.11.6.
- Is there a fix for This vulnerability?
- A patch was published on 2026-08-24: Fixed in version 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.
- Am I affected?
- Check whether you run vm2 (npm) or 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 exists in vm2 versions 3.11.3–3.11.6 where the Node.js crypto module is exposed to NodeVM sandboxes via a read-only proxy that preserves host-process authority for callable exports. An attacker with sandboxed code execution can call crypto.setEngine(path) with a filesystem path to an attacker-supplied native library; the operating-system dynamic loader executes the library constructor before OpenSSL validates the engine, achieving arbitrary native code execution in the host process. The attack requires only the crypto builtin and is fixed in version 3.11.7.
Affected products
- vm2 3.11.3 through 3.11.6
Timeline
- 2026-08-24: disclosed
- 2026-08-24: patched: Fixed in version 3.11.7