CVE-2026-92951: vm2 before 3.11.7 Module Allowlist Bypass via Custom Resolver
vm2 before 3.11.7 contains an incorrect authorization vulnerability in the external package allowlist check that uses non-exact substring matching instead of full package-name boundary validation. Attackers can bypass the allowlist by requiring a colliding package name that contains an allowlisted package substring, causing vm2 to load and execute unauthorized host packages in the host context.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
vm2to a version that resolves this vulnerability.Fixed in 3.11.7 - Compensating control
Ensure any dependency/loader package allowlist enforcement uses exact full package-name boundary validation (no substring matching) to prevent colliding package names from bypassing the allowlist.
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using npm/vm2 before 3.11.7 are exposed when they rely on the external package allowlist check and a custom resolver. The issue concerns loading external packages through that allowlist mechanism.
What does an attacker need to exploit this?
An attacker needs the ability to cause code in the vm2 environment to require a colliding package name containing the substring of an allowlisted package. No user interaction is required, and the supplied vector indicates low attack complexity with low privileges required.
What is the impact of a successful bypass?
The bypass can cause vm2 to load and execute an unauthorized host package in the host context. The provided severity vector indicates high impact to confidentiality, integrity, and availability, with scope changed.
How can I determine whether my configuration is affected?
Check whether your application uses vm2 before 3.11.7, configures an external package allowlist, and uses a custom resolver. Review whether package names that merely contain an allowlisted package name as a substring could be resolved.