CVE-2026-92954: Uncaught Exception in patriksimek vm2
CVE-2026-92954 affects the vm2 sandbox library for Node.js versions 3.10.0 through 3.11.7. The vulnerability involves unhandled rejected Promises returned from the host environment into the sandbox, which can cause the host Node.js process to terminate unexpectedly. This occurs because only Promises created inside the sandbox are properly wrapped with rejection handlers, while host Promises returned into the sandbox are not marked as handled. The issue was addressed and fixed in version 3.11.8.
AI Analysis
Technical Summary
The vm2 library versions >=3.10.0 and <=3.11.7 improperly handle Promises returned from the host realm into the sandbox. Specifically, these Promises are not marked as handled at the bridge boundary, unlike Promises created inside the sandbox which have rejection-swallowing handlers. The bridge installs host-side rejection sanitizers only when sandbox code calls .then/.catch/.finally, so if sandbox code invokes a host function returning a rejected Promise and ignores the return value, the host Promise remains unhandled. This triggers Node.js's default unhandled-rejection behavior, which terminates the host process. This vulnerability is an incomplete fix of a previous issue (GHSA-hw58-p9xv-2mjh) and is resolved in vm2 version 3.11.8.
Potential Impact
Exploitation of this vulnerability can cause the host Node.js process to terminate unexpectedly due to unhandled rejected Promises originating from the host environment but invoked within the sandbox. This can lead to denial of service conditions in applications using vulnerable versions of vm2.
Mitigation Recommendations
Upgrade vm2 to version 3.11.8 or later, where this issue is fixed. No other mitigations are indicated by the vendor advisory.
CVE-2026-92954: Uncaught Exception in patriksimek vm2
Description
CVE-2026-92954 affects the vm2 sandbox library for Node.js versions 3.10.0 through 3.11.7. The vulnerability involves unhandled rejected Promises returned from the host environment into the sandbox, which can cause the host Node.js process to terminate unexpectedly. This occurs because only Promises created inside the sandbox are properly wrapped with rejection handlers, while host Promises returned into the sandbox are not marked as handled. The issue was addressed and fixed in version 3.11.8.
CVSS v4.0
Score 9.2critical
Affected software
patriksimek
vm2
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vm2 library versions >=3.10.0 and <=3.11.7 improperly handle Promises returned from the host realm into the sandbox. Specifically, these Promises are not marked as handled at the bridge boundary, unlike Promises created inside the sandbox which have rejection-swallowing handlers. The bridge installs host-side rejection sanitizers only when sandbox code calls .then/.catch/.finally, so if sandbox code invokes a host function returning a rejected Promise and ignores the return value, the host Promise remains unhandled. This triggers Node.js's default unhandled-rejection behavior, which terminates the host process. This vulnerability is an incomplete fix of a previous issue (GHSA-hw58-p9xv-2mjh) and is resolved in vm2 version 3.11.8.
Potential Impact
Exploitation of this vulnerability can cause the host Node.js process to terminate unexpectedly due to unhandled rejected Promises originating from the host environment but invoked within the sandbox. This can lead to denial of service conditions in applications using vulnerable versions of vm2.
Mitigation Recommendations
Upgrade vm2 to version 3.11.8 or later, where this issue is fixed. No other mitigations are indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-17T12:43:31.527Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aac65c555bf5e2cf5fdf692
Added to database: 09/17/2026, 22:12:21 UTC
Last enriched: 09/17/2026, 22:16:56 UTC
Last updated: 09/18/2026, 02:27:39 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.