This logic flaw allows an attacker to manipulate the makeResolverFromLegacyOptions() function, leading to the creation of a resolver that exposes the host's vm2 module. By supplying a payload that initiates a NodeVM with nesting: true and a malicious require array, an attacker can escape the sandbox boundaries. Once escaped, the attacker can create an inner NodeVM with arbitrary builtin privileges, such as child_process, enabling the execution of arbitrary commands under the context of the host Node.js process. This vulnerability is addressed in vm2 version 3.11.7.

Impact

Successful exploitation allows for full sandbox escape and arbitrary code execution within the host environment. This impacts any application relying on vm2 for isolation of untrusted JavaScript, potentially leading to unauthorized data access, system-level command execution, and full compromise of the Node.js application process.

Recommendation

• Upgrade the vm2 dependency to version 3.11.7 or later across all applications utilizing this library to mitigate CVE-2026-92935.
• Audit all application code utilizing the NodeVM constructor to ensure the require configuration is strictly defined as an object rather than an array.
• Implement process-level sandboxing (e.g., containers, gVisor) as a secondary defense layer to limit the impact of a potential sandbox escape.