CVE-2026-44005: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in patriksimek vm2
vm2 is an open source vm/sandbox for Node.js. From 3.9.6 to 3.10.5, vm2's bridge exposes mutable proxies for real host-realm intrinsic prototypes and then forwards sandbox writes into the underlying host objects with otherReflectSet() and otherReflectDefineProperty(), which lets attacker-controlled JavaScript running in a default VM or inherited NodeVM mutate shared host Object.prototype, Array.prototype, and Function.prototype from inside the sandbox This vulnerability is fixed in 3.11.0.
AI Analysis
Technical Summary
The patriksimek vm2 Node.js sandbox versions from 3.9.6 up to but not including 3.11.0 contain a prototype pollution vulnerability (CWE-1321). The vulnerability arises because the vm2 bridge exposes mutable proxies for real host-realm intrinsic prototypes and forwards sandbox writes into the host environment using otherReflectSet() and otherReflectDefineProperty(). This allows malicious JavaScript code running inside a default VM or inherited NodeVM to modify shared host prototypes such as Object.prototype, Array.prototype, and Function.prototype. This can lead to severe integrity and availability impacts on the host environment. The vulnerability is addressed in vm2 version 3.11.0.
Potential Impact
An attacker can execute untrusted JavaScript code inside the vm2 sandbox and exploit this vulnerability to mutate global prototype objects in the host environment. This can lead to high-impact consequences including integrity violations and denial of service (availability impact). The CVSS v3.1 score is 10.0 (critical), reflecting network attack vector, no privileges required, no user interaction, and scope change with high impact on integrity and availability.
Mitigation Recommendations
This vulnerability is fixed in vm2 version 3.11.0. Users should upgrade to version 3.11.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fix in 3.11.0, so users should verify the upgrade and consult the official vm2 release notes for confirmation. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes.
CVE-2026-44005: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in patriksimek vm2
Description
vm2 is an open source vm/sandbox for Node.js. From 3.9.6 to 3.10.5, vm2's bridge exposes mutable proxies for real host-realm intrinsic prototypes and then forwards sandbox writes into the underlying host objects with otherReflectSet() and otherReflectDefineProperty(), which lets attacker-controlled JavaScript running in a default VM or inherited NodeVM mutate shared host Object.prototype, Array.prototype, and Function.prototype from inside the sandbox This vulnerability is fixed in 3.11.0.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The patriksimek vm2 Node.js sandbox versions from 3.9.6 up to but not including 3.11.0 contain a prototype pollution vulnerability (CWE-1321). The vulnerability arises because the vm2 bridge exposes mutable proxies for real host-realm intrinsic prototypes and forwards sandbox writes into the host environment using otherReflectSet() and otherReflectDefineProperty(). This allows malicious JavaScript code running inside a default VM or inherited NodeVM to modify shared host prototypes such as Object.prototype, Array.prototype, and Function.prototype. This can lead to severe integrity and availability impacts on the host environment. The vulnerability is addressed in vm2 version 3.11.0.
Potential Impact
An attacker can execute untrusted JavaScript code inside the vm2 sandbox and exploit this vulnerability to mutate global prototype objects in the host environment. This can lead to high-impact consequences including integrity violations and denial of service (availability impact). The CVSS v3.1 score is 10.0 (critical), reflecting network attack vector, no privileges required, no user interaction, and scope change with high impact on integrity and availability.
Mitigation Recommendations
This vulnerability is fixed in vm2 version 3.11.0. Users should upgrade to version 3.11.0 or later to remediate this issue. Patch status is not explicitly stated beyond the fix in 3.11.0, so users should verify the upgrade and consult the official vm2 release notes for confirmation. No vendor advisory content is provided to indicate alternative mitigations or temporary fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-04T21:24:36.505Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a04ba22cbff5d8610f482c5
Added to database: 5/13/2026, 5:51:30 PM
Last enriched: 5/13/2026, 6:07:35 PM
Last updated: 5/14/2026, 6:47:34 AM
Views: 5
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.