A critical authorization bypass vulnerability in the vm2 sandbox allows authenticated attackers to execute arbitrary code within the host context, posing a severe risk to system integrity.

This flaw exists due to the use of non-exact substring matching for package allowlist validation, enabling an attacker with low-level privileges to load unauthorized host packages. By utilizing package name collisions, an attacker can escape the sandbox environment and achieve full code execution on the host system.

The ability to execute code outside of the intended sandbox environment represents a total compromise of the application runtime. Given the CVSS score of 9.9, this vulnerability could lead to unauthorized data access, complete system takeover, and the potential for lateral movement within the network, resulting in significant operational and reputational damage.

Immediate Action: Update the patriksimek vm2 package to version 3.11.7 or later to implement proper package name boundary validation.

Proactive Monitoring: Review application logs for unusual package loading patterns or attempts to access restricted host modules that deviate from established operational baselines.

Compensating Controls: Implement strict environment-level sandboxing or containerization policies to limit the privileges of processes utilizing vm2, thereby reducing the impact of a successful sandbox escape.

Public Exploit Available: Unknown

This vulnerability is highly critical due to the potential for complete sandbox escape and host compromise. Organizations utilizing the vm2 package must prioritize updating to version 3.11.7 immediately. Failure to patch this flaw leaves the host environment susceptible to arbitrary code execution by any authenticated user capable of triggering the vulnerable package resolution logic.