[ CVE-2026-92940 · Published 17 Sep 2026 ]
vm2 exposes host HTTPS credentials and TLS traffic through globalAgent
[ Why it matters ]Priority signals
- Critical severity: CVSS 10.0
[ Description ]Official description
vm2 versions 3.11.3 through 3.11.6 expose the host process's real https.globalAgent to sandboxed code when a NodeVM is explicitly configured to allow require('https'). The builtin loader wraps host modules in a read-only proxy, but method calls such as Agent.prototype.on() are forwarded to the underlying host object, so sandbox code can register a listener for the agent's 'free' event. When an unrelated host HTTPS request releases a pooled connection, the listener receives the live host request options and the host TLSSocket, allowing sandboxed code to read the host's Authorization header and private destination host/port, attach a data listener to the released socket and read subsequent host response bodies in plaintext, and issue attacker-chosen authenticated requests using the stolen credentials. The issue is fixed in 3.11.7.
[ Fixes ]Fixes and patches
- vm2 3.11.7Fixed version · GitHub Advisories · npm package vm2: upgrade to 3.11.7 or later (affected >= 3.11.3, <= 3.11.6)
[ Packages ]Affected open-source packages
- vm2 npmAffected >= 3.11.3, <= 3.11.6 · fixed in 3.11.7 · GHSA-h85j-hv3c-qfgq