CVE-2026-47139: CWE-693: Protection Mechanism Failure in patriksimek vm2
vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM supports excluding public network builtins from the wildcard builtin option. With this configuration direct access to http, https, http2, net, dgram, tls, dns, and dns/promises is blocked. However, Node.js also exposes underscored internal HTTP builtins such as _http_client and _http_server. These are not blocked when the public modules are excluded. Sandboxed code can use these internal builtins to make outbound HTTP requests and open listening HTTP sockets even though the public network modules are denied. This issue has been patched in version 3.11.4.
AI Analysis
Technical Summary
vm2 is an open source sandbox for Node.js that allows restricting access to certain built-in modules. Before version 3.11.4, when the NodeVM was configured to exclude public network builtins (http, https, http2, net, dgram, tls, dns, dns/promises), it failed to block internal underscored HTTP builtins (_http_client and _http_server). These internal modules could be used by sandboxed code to make outbound HTTP requests and open listening HTTP sockets, circumventing the intended network access restrictions. This represents a protection mechanism failure (CWE-693). The issue was fixed in vm2 version 3.11.4.
Potential Impact
Sandboxed code can bypass network restrictions by accessing internal HTTP modules not blocked by the exclusion of public network builtins. This allows unauthorized outbound HTTP requests and opening of listening sockets, potentially leading to data exfiltration or unauthorized network communication. The CVSS score of 8.6 reflects high impact on confidentiality with no impact on integrity or availability.
Mitigation Recommendations
Upgrade vm2 to version 3.11.4 or later, where this issue is patched. No other mitigation is indicated. Patch status is not explicitly stated in the vendor advisory fields, but the description confirms the fix in 3.11.4.
CVE-2026-47139: CWE-693: Protection Mechanism Failure in patriksimek vm2
Description
vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM supports excluding public network builtins from the wildcard builtin option. With this configuration direct access to http, https, http2, net, dgram, tls, dns, and dns/promises is blocked. However, Node.js also exposes underscored internal HTTP builtins such as _http_client and _http_server. These are not blocked when the public modules are excluded. Sandboxed code can use these internal builtins to make outbound HTTP requests and open listening HTTP sockets even though the public network modules are denied. This issue has been patched in version 3.11.4.
CVSS v3.1
Score 8.6high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
vm2 is an open source sandbox for Node.js that allows restricting access to certain built-in modules. Before version 3.11.4, when the NodeVM was configured to exclude public network builtins (http, https, http2, net, dgram, tls, dns, dns/promises), it failed to block internal underscored HTTP builtins (_http_client and _http_server). These internal modules could be used by sandboxed code to make outbound HTTP requests and open listening HTTP sockets, circumventing the intended network access restrictions. This represents a protection mechanism failure (CWE-693). The issue was fixed in vm2 version 3.11.4.
Potential Impact
Sandboxed code can bypass network restrictions by accessing internal HTTP modules not blocked by the exclusion of public network builtins. This allows unauthorized outbound HTTP requests and opening of listening sockets, potentially leading to data exfiltration or unauthorized network communication. The CVSS score of 8.6 reflects high impact on confidentiality with no impact on integrity or availability.
Mitigation Recommendations
Upgrade vm2 to version 3.11.4 or later, where this issue is patched. No other mitigation is indicated. Patch status is not explicitly stated in the vendor advisory fields, but the description confirms the fix in 3.11.4.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T19:50:18.696Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a2c1a23e617e2d8347eb1dd
Added to database: 6/12/2026, 2:39:31 PM
Last enriched: 6/12/2026, 2:55:35 PM
Last updated: 6/13/2026, 4:56:22 AM
Views: 10
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.