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.10.1, <= 3.11.6; Patrik Simek Vm2 3.10.1 through 3.11.6.

Is there a fix for This vulnerability?

Yes: fixed in 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.

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.

vm2 sandbox escape via WebAssembly.compileStreaming Promise species bypass

Q: Which products and versions are affected?

vm2 (npm) >= 3.10.1, <= 3.11.6; Patrik Simek Vm2 3.10.1 through 3.11.6.

Q: Is there a fix for This vulnerability?

Yes: fixed in 3.11.7. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a software library.

Q: 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.

Severity: critical · CVSS 10 · Published 2026-09-17

vm2 is a JavaScript sandbox library used to safely execute untrusted code in isolation. A critical vulnerability allows attackers running code in a default vm2 sandbox on Node.js 26 to escape the sandbox and gain access to the host system's filesystem and other capabilities. The exploit requires no special configuration and works immediately when code executes within the sandbox.

Technologies: vm2 (npm), Patrik Simek Vm2. Vendors: npm, Patrik Simek.

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.10.1, <= 3.11.6; Patrik Simek Vm2 3.10.1 through 3.11.6.
Is there a fix for This vulnerability?: Yes: fixed in 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.

How to fix

Fixed in: 3.11.7

Technical details

vm2 versions 3.10.1 through 3.11.6 contain a sandbox escape triggered via WebAssembly.compileStreaming and WebAssembly.instantiateStreaming, which can produce a raw host-realm Promise. An attacker can manipulate Symbol.species on Promise.prototype.finally to intercept the rejection handler, receive a host error object, and walk the constructor chain to recover the host process object, gaining full Node.js capabilities including module access. This is a bypass of the JSPI-related fix in earlier patches.

Affected products

Patrik Simek vm2 3.10.1 through 3.11.6

Timeline

2026-09-17: disclosed
2026-10-05: advisory: advisory withdrawn as duplicate of GHSA-wjwh-qqvp-g4p4

References

https://api.github.com/users/portyu9

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.