{"uuid": "c9bf667a-34c4-4412-89a6-b874ee63219d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-92940", "type": "seen", "source": "https://gist.github.com/alon710/8668fd6a23c76d394335860a03691015", "content": "# CVE-2026-92940: CVE-2026-92940: Host-Realm Credential Exposure and Socket Hijacking via globalAgent in vm2\n\n> **CVSS Score:** 10.0\n> **Published:** 2026-10-01\n> **Full Report:** https://cvereports.com/reports/CVE-2026-92940\n\n## Summary\nA critical vulnerability in the Node.js sandbox library vm2 allows sandboxed code to retrieve the process-wide http.globalAgent and https.globalAgent singletons. By attaching event listeners to these host-realm emitters, sandboxed code can intercept host-realm network requests, capturing sensitive Authorization headers and hijacking active TLSSocket streams.\n\n## TL;DR\nA sandbox escape in vm2 (versions 3.11.3 to 3.11.6) allows untrusted code to access and hook the host process-wide http/https globalAgent. This enables unauthenticated attackers to steal sensitive headers (like Bearer tokens) and hijack active sockets during unrelated host-realm requests.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-668: Exposure of Resource to Wrong Sphere\n- **Attack Vector**: Network (AV:N)\n- **CVSS v3.1 Score**: 10.0 (Critical)\n- **EPSS Score**: 0.00474 (Percentile: 38.70%)\n- **Impact**: Host Credential Disclosure & Transport Socket Hijacking\n- **Exploit Status**: Proof-of-Concept (PoC) available via official regression test suite\n- **CISA KEV Status**: Not Listed\n\n## Affected Systems\n\n- vm2 (npm package)\n- **vm2**: >= 3.11.3, <= 3.11.6 (Fixed in: `3.11.7`)\n\n## Mitigation\n\n- Upgrade vm2 to version 3.11.7 or newer to apply member-level neutralization on built-in HTTP/HTTPS modules.\n- Disable the 'http' and 'https' built-in modules inside the NodeVM configuration settings to remove the attack vector entirely.\n- Implement outbound network requests outside of the sandbox boundary using a strictly validated custom host-realm API rather than exposing native raw network modules.\n- Transition application architectures away from vm2 to modern isolated runtimes, such as isolated-vm or VM containers.\n\n**Remediation Steps:**\n1. Locate and audit package.json and project lockfiles for vm2 references within versions 3.11.3 and 3.11.6.\n2. Run 'npm install vm2@3.11.7' or 'yarn upgrade vm2@3.11.7' to deploy the patched library version.\n3. Review initialization scripts of NodeVM to ensure that 'http' and 'https' are absent from the require.builtin array.\n4. Validate the fix by executing the official regression test to ensure host globalAgent is no longer reachable from the sandbox environment.\n\n## References\n\n- [GHSA-h85j-hv3c-qfgq Security Advisory](https://github.com/patriksimek/vm2/security/advisories/GHSA-h85j-hv3c-qfgq)\n- [VulnCheck Vulnerability Report](https://www.vulncheck.com/advisories/vm2-3.11.3-through-3.11.6-https-credential-exposure-via-globalagent)\n- [Official Patch Commit](https://github.com/patriksimek/vm2/commit/aa146a77f859325e079f3bfbfe6d8309af483daa)\n- [vm2 v3.11.7 Release Tag](https://github.com/patriksimek/vm2/releases/tag/v3.11.7)\n- [NVD CVE-2026-92940 Details](https://nvd.nist.gov/vuln/detail/CVE-2026-92940)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-92940) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-10-02T01:30:30.000000Z"}