Is CVE-2026-92960 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92960 being exploited in the wild.

How severe is CVE-2026-92960?

Critical severity, with a CVSS score of 10, published 17 September 2026.

Which products and versions are affected?

vm2 (npm) SEMVER:introduced=0,fixed=3.11.6.

Is there a fix for CVE-2026-92960?

Yes. vm2 (npm): upgrade to 3.11.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-92960 attacked?

It is attacked over the network.

Am I affected by CVE-2026-92960?

Check whether you run vm2 (npm) 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.

CVE-2026-92960: vm2 NodeVM builtin wildcard sandbox escape via os and dns modules

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

vm2 is a JavaScript sandboxing library used to safely execute untrusted code in isolation. When configured with the documented "full builtins" pattern (builtin: ['*']), the sandbox incorrectly exposes the os and dns Node.js modules, allowing an attacker to read sensitive host information (network topology, user credentials, system telemetry) and perform DNS hijacking that affects the entire host process, defeating the sandbox isolation guarantee.

Technologies: vm2 (npm). Vendors: npm.

Quick answers

Is CVE-2026-92960 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92960 being exploited in the wild.
How severe is CVE-2026-92960?: Critical severity, with a CVSS score of 10, published 17 September 2026.
Which products and versions are affected?: vm2 (npm) SEMVER:introduced=0,fixed=3.11.6.
Is there a fix for CVE-2026-92960?: Yes. vm2 (npm): upgrade to 3.11.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-92960 attacked?: It is attacked over the network.
Am I affected by CVE-2026-92960?: Check whether you run vm2 (npm) 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

vm2 (npm): upgrade to 3.11.6 or later
```
npm install vm2@3.11.6
```

Technical details

This vulnerability is a sandbox escape in vm2's NodeVM due to incomplete module blocklisting. The os and dns builtins are not included in the DANGEROUS_BUILTINS set despite satisfying the same criteria established in GHSA-9g8x-92q2-p28f: they expose and mutate global host-process state that cannot be localized by vm.readonly() proxies. Attack requires NodeVM configuration with builtin: ['*'] (the documented recommended pattern) and no manual -os/-dns exclusions. An attacker controlling sandbox code can call os.userInfo(), os.networkInterfaces(), os.hostname() to exfiltrate host deployment details, and invoke dns.setServers() to perform process-wide DNS hijacking affecting all host outbound network calls. No authentication or user interaction is required. The fix adds os and dns to DANGEROUS_BUILTINS in patched version 3.11.6.

Affected products

vm2 vm2 <= 3.11.5

Identifiers

CVE-2026-92960
GHSA-m5w8-4gq2-6f8x

Timeline

2026-08-17: disclosed
2026-08-14: patched: Version 3.11.6

References

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