CVE-2026-44000: CWE-693: Protection Mechanism Failure in patriksimek vm2
vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, a sandbox boundary violation in vm2 allows host object identity to cross into the sandbox through host Promise resolution. When a host-side Promise that resolves to a host object is exposed to the sandbox, the value delivered to the sandbox .then() callback preserves host identity. This allows the sandbox to interact with the host object directly, including performing identity checks using host-side WeakMap and mutating host object state from inside the sandbox. This behavior occurs because the Promise fulfillment wrapper uses ensureThis() instead of the stronger cross-realm conversion path (from() / proxy wrapping). If no prototype mapping is found, ensureThis() returns the original object. As a result, objects resolved by host Promises can cross the sandbox boundary without proper isolation. This vulnerability is fixed in 3.11.0.
AI Analysis
Technical Summary
The vm2 Node.js sandbox prior to version 3.11.0 contains a protection mechanism failure (CWE-693) where host object identity can leak into the sandbox via host Promise resolution. When a host Promise resolves to a host object and is exposed to the sandbox, the sandbox's .then() callback receives the original host object without proper isolation. This is caused by the Promise fulfillment wrapper using ensureThis() rather than a secure cross-realm conversion path, allowing sandbox code to interact with and mutate host objects directly. The vulnerability is addressed in vm2 3.11.0.
Potential Impact
An attacker controlling sandboxed code can bypass the intended isolation boundary by accessing and mutating host objects directly through resolved Promises. This can lead to unauthorized information disclosure and integrity violations within the host environment. There is no indication of availability impact. The CVSS score is 6.5 (medium severity), reflecting network attack vector with low complexity and no privileges required.
Mitigation Recommendations
Upgrade vm2 to version 3.11.0 or later, where this vulnerability is fixed. Patch status is not explicitly stated in the vendor advisory, but the description confirms the issue is resolved in 3.11.0. No other mitigations are indicated.
CVE-2026-44000: CWE-693: Protection Mechanism Failure in patriksimek vm2
Description
vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, a sandbox boundary violation in vm2 allows host object identity to cross into the sandbox through host Promise resolution. When a host-side Promise that resolves to a host object is exposed to the sandbox, the value delivered to the sandbox .then() callback preserves host identity. This allows the sandbox to interact with the host object directly, including performing identity checks using host-side WeakMap and mutating host object state from inside the sandbox. This behavior occurs because the Promise fulfillment wrapper uses ensureThis() instead of the stronger cross-realm conversion path (from() / proxy wrapping). If no prototype mapping is found, ensureThis() returns the original object. As a result, objects resolved by host Promises can cross the sandbox boundary without proper isolation. This vulnerability is fixed in 3.11.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vm2 Node.js sandbox prior to version 3.11.0 contains a protection mechanism failure (CWE-693) where host object identity can leak into the sandbox via host Promise resolution. When a host Promise resolves to a host object and is exposed to the sandbox, the sandbox's .then() callback receives the original host object without proper isolation. This is caused by the Promise fulfillment wrapper using ensureThis() rather than a secure cross-realm conversion path, allowing sandbox code to interact with and mutate host objects directly. The vulnerability is addressed in vm2 3.11.0.
Potential Impact
An attacker controlling sandboxed code can bypass the intended isolation boundary by accessing and mutating host objects directly through resolved Promises. This can lead to unauthorized information disclosure and integrity violations within the host environment. There is no indication of availability impact. The CVSS score is 6.5 (medium severity), reflecting network attack vector with low complexity and no privileges required.
Mitigation Recommendations
Upgrade vm2 to version 3.11.0 or later, where this vulnerability is fixed. Patch status is not explicitly stated in the vendor advisory, but the description confirms the issue is resolved in 3.11.0. No other mitigations are indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-04T20:24:31.918Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a04ba1fcbff5d8610f48259
Added to database: 5/13/2026, 5:51:27 PM
Last enriched: 5/13/2026, 6:08:11 PM
Last updated: 5/13/2026, 6:57:43 PM
Views: 2
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.
External Links
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.