Uncaught Exception Affecting org.webjars.npm:vm2 package, versions [,3.12.2)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGWEBJARSNPM-20158391
- published13 Oct 2026
- disclosed27 Sept 2026
- creditUnknown
Introduced: 27 Sep 2026
NewCVE-2026-100722 (opens in a new tab)How to fix?
Upgrade org.webjars.npm:vm2 to version 3.12.2 or higher.
Overview
org.webjars.npm:vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules.
Affected versions of this package are vulnerable to Uncaught Exception via the host-to-sandbox promise delivery path in lib/bridge.js, where a host promise reaching the sandbox through the construct trap, a host getter or data property, or as an argument to a sandbox callback carries no rejection reaction. When sandbox code ignores such a promise, Node's unhandledRejection policy is triggered, terminating the host process. An attacker controlling sandbox code can cause this condition through any of those delivery routes without requiring filesystem access, a Node builtin, nested VMs, or host compromise.