CVE-2026-92940

10.0

patriksimek · vm2

An unauthenticated sandbox escape in vm2 allows sandboxed code to access the host process's https.globalAgent, leading to credential theft and unauthorized request execution.

Executive summary

A critical vulnerability in the vm2 library allows sandboxed code to bypass security boundaries and compromise host process credentials, requiring an immediate update to version 3.11.7.

Vulnerability

This is an exposure of resource to the wrong sphere (CWE-668) where the https.globalAgent is improperly exposed to sandboxed code. An unauthenticated attacker can register listeners for host events to intercept sensitive Authorization headers and initiate authenticated requests on behalf of the host process.

Business impact

The vulnerability carries a CVSS score of 10.0, indicating the highest level of severity. Successful exploitation allows for complete compromise of host-level confidentiality and integrity, as attackers can steal sensitive credentials and perform unauthorized actions within the host environment. This poses a severe risk of data exfiltration and secondary attacks against internal infrastructure.

Remediation

Immediate Action: Update the patriksimek vm2 library to version 3.11.7 or later to implement the necessary security fix.

Proactive Monitoring: Review application logs for unusual outbound HTTPS requests or unexpected registration of event listeners within NodeVM instances.

Compensating Controls: If immediate patching is not feasible, restrict the use of require('https') within NodeVM configurations to prevent the vulnerable code path from being triggered.

Exploitation status

Public Exploit Available: No (exploit_available: unknown)

Analyst recommendation

Given the critical CVSS score of 10.0, this vulnerability must be treated as a priority. Organizations utilizing the vm2 library in environments where untrusted code is executed must upgrade to version 3.11.7 immediately to prevent sandbox escape and subsequent host compromise.

More patriksimek CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by Forrof, per the CVE Program record.