Description Summary:
The vm2 sandbox for Node.js fails to block prototype chain manipulation, allowing unauthenticated attackers to escape the sandbox and execute arbitrary host commands.

Executive Summary:
A critical sandbox escape vulnerability in the patriksimek vm2 library allows unauthenticated attackers to achieve arbitrary host command execution.

Vulnerability Details

CVE-ID: CVE-2026-47698

Affected Software: patriksimek vm2

Affected Versions: < 3.11.6

Vulnerability: This vulnerability is a sandbox escape flaw stemming from improper control of dynamically managed code resources (CWE-913). By leveraging stacked indirection through Function.prototype.call, an unauthenticated attacker can manipulate host intrinsic prototypes to execute arbitrary code on the host system.

Business Impact

The ability to escape a sandbox environment and execute arbitrary host commands represents a total compromise of the host system. Given the CVSS score of 9.8, this vulnerability poses an extreme risk to data confidentiality, integrity, and availability, potentially leading to full system takeover and lateral movement within the network.

Remediation Plan

Immediate Action: Update the patriksimek vm2 library to version 3.11.6 or later immediately.

Proactive Monitoring: Review application logs for unusual sandbox behavior or execution attempts involving internal prototype chain modifications.

Compensating Controls: Since this is a library-level vulnerability, ensure that the application is running with the principle of least privilege, minimizing the impact if the host is compromised.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of Aug 17, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly dangerous due to the nature of sandbox escapes, which bypass the primary security boundary intended to isolate untrusted code.

Analyst Recommendation

This vulnerability is highly critical and requires immediate attention. Organizations utilizing vm2 to sandbox untrusted code must prioritize the upgrade to version 3.11.6 to prevent potential remote code execution and full host compromise.

Description Summary:
A sandbox escape vulnerability in the vm2 library allows attackers to bypass security restrictions and execute arbitrary host commands by manipulating Error.cause.

Executive Summary:
A critical sandbox escape in the vm2 library allows attackers to break out of the virtual environment and execute arbitrary commands on the host system.

Vulnerability Details

CVE-ID: CVE-2026-47686

Affected Software: patriksimek vm2

Affected Versions: < 3.11.6

Vulnerability: The vulnerability exists in the handleException function, which fails to properly sanitize the Error.cause property. An attacker can leverage this failure to obtain references to powerful host objects, such as the process object, enabling the execution of arbitrary host-level commands.

Business Impact

This flaw effectively nullifies the security benefits of the sandbox, allowing for full host compromise. Given the prevalence of vm2 in Node.js applications, this could lead to widespread data breaches, unauthorized server access, and complete system takeover. The 9.9 CVSS score reflects the extreme risk associated with a successful sandbox escape.

Remediation Plan

Immediate Action: Update the vm2 dependency to version 3.11.6 or later immediately. Verify that all downstream applications have successfully integrated the patched library version.

Proactive Monitoring: Monitor for unusual child process spawns or unauthorized file system access originating from the Node.js application process. Review application logs for unexpected error patterns.

Compensating Controls: Implement strict OS-level sandboxing (e.g., containers, gVisor, or restricted user accounts) to limit the potential impact if the application sandbox is bypassed.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of Aug 17, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is highly complex but represents a critical failure of the core isolation mechanism.

Analyst Recommendation

The severity of a sandbox escape cannot be overstated, as it represents a fundamental breach of trust in the application security architecture. Development teams must prioritize this update to ensure the integrity of their Node.js environments.

Description Summary:
The vm2 sandbox library for Node.js is vulnerable to resource exhaustion due to insufficient limits on resource allocation, potentially leading to denial of service.

Executive Summary:
The vm2 sandbox library for Node.js contains a resource allocation vulnerability that can be leveraged by an unauthenticated attacker to cause a denial of service.

Vulnerability Details

CVE-ID: CVE-2026-47683

Affected Software: patriksimek vm2

Affected Versions: < 3.11.6

Vulnerability: This is a resource allocation vulnerability (CWE-770) where the software fails to properly limit or throttle resources, allowing an unauthenticated attacker to trigger excessive consumption.

Business Impact

An attacker can exploit this vulnerability to exhaust system resources, resulting in a denial of service for applications relying on the vm2 sandbox. This can lead to significant service disruption and downtime for any web services or internal tools utilizing this library. The CVSS score of 8.7 highlights the severity of this availability risk.

Remediation Plan

Immediate Action: Update the vm2 dependency to version 3.11.6 or later to enforce proper resource limits.

Proactive Monitoring: Monitor CPU and memory usage patterns for Node.js applications to identify potential resource exhaustion attacks.

Compensating Controls: Implement rate limiting and resource quotas at the application or container level to restrict the impact of potential sandbox escapes or exhaustion attempts.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 18, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The lack of resource throttling makes the sandbox inherently susceptible to DoS if not properly configured.

Analyst Recommendation

Organizations using the vm2 sandbox library should perform an immediate audit of their dependencies and update to the patched version. Ensuring that the sandbox is correctly configured with resource limits is essential to maintaining service availability.

Description Summary:
The vm2 sandbox for Node.js is vulnerable to a sandbox escape that allows arbitrary code execution in the host process when using WebAssembly JSPI.

Executive Summary:
A critical sandbox escape vulnerability in vm2 allows attackers to break out of the virtual machine and execute arbitrary code on the host system.

Vulnerability Details

CVE-ID: CVE-2026-47210

Affected Software: vm2

Affected Versions: Prior to version 3.11.4

Vulnerability: The flaw occurs when untrusted code is executed with async support on runtimes exposing WebAssembly JSPI, allowing a Promise to bypass security hardening and break the sandbox boundary.

Business Impact

By escaping the sandbox, an attacker can transition from executing restricted code to executing arbitrary code on the underlying host process. This results in a full system compromise, granting the attacker the same permissions as the Node.js process. With a CVSS score of 9.8, this is a highly dangerous flaw for any application relying on vm2 for isolation.

Remediation Plan

Immediate Action: Update the vm2 dependency in all projects to version 3.11.4 or later.

Proactive Monitoring: Monitor for unexpected child processes or unusual file system/network activity originating from the Node.js process running the vm2 sandbox.

Compensating Controls: Ensure the Node.js process is running with the principle of least privilege, minimizing the impact of a potential sandbox escape.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of Jun 12, 2026, a public exploit exists for this vulnerability. Given the nature of sandbox escapes, the risk of exploitation is high.

Analyst Recommendation

Sandboxing libraries are security-critical components. Because this vulnerability allows for full host compromise, it is imperative that all developers using vm2 update to the latest patched version immediately to maintain the integrity of their application environment.

Description Summary:
The vm2 library is susceptible to a sandbox escape due to a flaw in the BaseHandler.set method which incorrectly ignores the receiver parameter.

Executive Summary:
A critical sandbox escape vulnerability in vm2 allows attackers to escape the sandbox and execute code on the host system.

Vulnerability Details

CVE-ID: CVE-2026-47209

Affected Software: vm2 (Node.js sandbox)

Affected Versions: vm2, npm, <= 3.11.3

Vulnerability: This is a sandbox escape caused by an improper implementation of the property setting mechanism. Specifically, the BaseHandler.set method fails to correctly handle the receiver parameter, allowing sandboxed code to manipulate host-side objects and execute arbitrary code.

Business Impact

The vulnerability carries a CVSS score of 8.6, indicating a high risk of host-level compromise. Successful exploitation grants an attacker the ability to break out of the sandbox confinement, leading to potential unauthorized access, data exfiltration, or complete host system takeover.

Remediation Plan

Immediate Action: Upgrade to vm2 version 3.11.4 or higher to apply the necessary security fixes for the bridge handler.

Proactive Monitoring: Review application logs for unusual sandbox behavior or attempts to perform unauthorized property modifications within the NodeVM environment.

Compensating Controls: Deploy the application within an isolated environment with minimal privileges to reduce the impact of a potential sandbox escape.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of June 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The vulnerability represents a direct threat to the security boundaries provided by vm2. Administrators must prioritize updating to version 3.11.4 to mitigate the risk of host-level compromise and ensure the continued efficacy of their sandboxing strategy.

Description Summary:
A sandbox breakout vulnerability in vm2 allows unauthenticated attackers to execute arbitrary commands on the host system via promise manipulation.

Executive Summary:
A critical sandbox breakout in vm2 (versions <= 3.11.3) allows unauthenticated attackers to achieve arbitrary command execution on the host system.

Vulnerability Details

CVE-ID: CVE-2026-47208

Affected Software: vm2 (vm2)

Affected Versions: vm2 prior to version 3.11.4, or versions <= 3.11.3.

Vulnerability: This is a sandbox breakout vulnerability resulting from improper handling of the localPromise constructor. Attackers can supply a custom reject method that triggers a breakout, allowing them to escape the sandbox and execute commands with the privileges of the host process.

Business Impact

The capability to escape the sandbox and execute arbitrary commands on the host machine is a catastrophic security failure. Given the CVSS score of 10.0, this vulnerability provides a direct path for attackers to gain full control over the host system, leading to total data loss, system destruction, or deep-seated persistent access.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.4 immediately to patch the promise handling logic.

Proactive Monitoring: Monitor host systems for unexpected shell command executions or child processes being spawned by the Node.js application process.

Compensating Controls: Use container isolation technologies (like Docker or Kubernetes security contexts) to restrict the potential damage if the sandbox is breached.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of Jun 12, 2026, public exploit code is available for this vulnerability. The combination of high impact and available exploit code makes this a top-priority remediation item.

Analyst Recommendation

The risk posed by this sandbox escape is extreme. Security teams should treat this as an urgent priority; the availability of functional exploit code necessitates immediate patching to mitigate the risk of host-level command execution.

Description Summary:
An incomplete denylist of Node.js builtins in vm2 allows unauthenticated attackers to escape the sandbox and execute code in the host process.

Executive Summary:
A critical vulnerability in vm2 (versions up to 3.11.3) permits unauthenticated attackers to escape the sandbox by exploiting missing restrictions on sensitive Node.js builtins.

Vulnerability Details

CVE-ID: CVE-2026-47140

Affected Software: vm2 (vm2)

Affected Versions: vm2 prior to version 3.11.4, or versions up to 3.11.3.

Vulnerability: The NodeVM sandbox fails to sufficiently restrict access to sensitive built-in modules, specifically 'process' and 'inspector/promises'. These modules provide unauthenticated attackers with primitives necessary to interact with the host-side environment, effectively bypassing all sandbox isolation.

Business Impact

The ability to access host-side execution primitives from within a sandbox renders the isolation provided by vm2 ineffective. With a CVSS score of 10.0, this vulnerability allows for full system compromise, posing a major risk of unauthorized data access, privilege escalation, and persistent threats to the underlying host infrastructure.

Remediation Plan

Immediate Action: Upgrade vm2 to version 3.11.4 to incorporate the updated denylist and restrict access to dangerous Node.js builtins.

Proactive Monitoring: Audit application code for any usage of dangerous modules and monitor system logs for signs of anomalous process execution originating from sandboxed environments.

Compensating Controls: If upgrading is delayed, use system-level policies (e.g., AppArmor or SELinux) to restrict the capabilities of the process running the vm2 sandbox.

Exploitation Status

Public Exploit Available: False

Analyst Notes: As of Jun 12, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

While no public exploits are currently identified, the severity of a sandbox breakout via built-in modules is extreme. Organizations must prioritize the update to version 3.11.4 to ensure that sandbox boundaries are properly enforced against known dangerous primitives.

Description Summary:
A vulnerability in the vm2 library's NodeVM component allows attackers to bypass network exclusions and perform SSRF-style attacks via the wildcard '*' option.

Executive Summary:
A high-severity flaw in the vm2 library's NodeVM component permits unauthorized network access and potential Server-Side Request Forgery (SSRF) attacks.

Vulnerability Details

CVE-ID: CVE-2026-47139

Affected Software: vm2 (Node.js sandbox)

Affected Versions: vm2, npm, <= 3.11.3

Vulnerability: The vulnerability resides in how the NodeVM component handles the '*' (wildcard) option for built-in modules. This flaw allows sandboxed code to bypass configured network security exclusions, facilitating SSRF-style attacks against the host or internal network.

Business Impact

With a CVSS score of 8.6, this vulnerability poses a severe threat to internal network security. An attacker capable of executing code within the sandbox could leverage this flaw to probe internal services, bypass firewall restrictions, or interact with sensitive internal APIs that are otherwise unreachable from the public internet.

Remediation Plan

Immediate Action: Update to vm2 version 3.11.4 or later to address the insecure handling of the wildcard module option.

Proactive Monitoring: Inspect outbound network traffic from sandboxed environments for anomalous requests directed toward internal network segments.

Compensating Controls: Enforce egress filtering at the network level to restrict the reach of sandboxed processes, even if the sandbox configuration is bypassed.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of June 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Organizations relying on vm2 for process isolation must update to 3.11.4 immediately. Given the potential for SSRF attacks, this should be treated with high urgency to maintain the integrity of the internal network architecture.

Description Summary:
An improper security check implementation in vm2 allows unauthenticated attackers to bypass sandbox restrictions and achieve remote code execution.

Executive Summary:
A critical security bypass in vm2 (versions up to 3.11.3) allows unauthenticated attackers to escape the sandbox and execute arbitrary code on the host.

Vulnerability Details

CVE-ID: CVE-2026-47137

Affected Software: vm2 (vm2)

Affected Versions: vm2 prior to version 3.11.4, or versions up to 3.11.3.

Vulnerability: The vulnerability stems from a flawed strict equality check in the nodevm.js configuration. By omitting the 'require' option entirely, an attacker can bypass the intended security guard, forcing the application into an insecure configuration that enables sandbox escape.

Business Impact

This flaw effectively neutralizes the security controls of the vm2 sandbox, allowing attackers to escape into the host environment. With a CVSS score of 10.0, successful exploitation leads to full remote code execution, granting attackers the ability to steal sensitive data, deploy malware, or disrupt critical business operations.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.4 to resolve the logic error in the security configuration check.

Proactive Monitoring: Review application configurations to ensure that security options are explicitly defined rather than relying on default values that may be subject to bypass.

Compensating Controls: Utilize a Web Application Firewall (WAF) or Runtime Application Self-Protection (RASP) tool to detect and block malicious payloads attempting to instantiate sandboxes with invalid configurations.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of Jun 12, 2026, public exploit code is available for this vulnerability. The presence of functional exploits necessitates immediate patching to prevent unauthorized host access.

Analyst Recommendation

The vulnerability is a direct failure of the security logic in the vm2 library. Given the critical nature of the impact and the availability of exploitation methods, organizations should treat this update as an emergency patch to prevent potential system compromise.

Description Summary:
The vm2 library contains a sandbox escape vulnerability caused by incomplete overrides of the global Symbol.for function and flaws in proxy-based bridge write-trap handlers.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library allows malicious code to break out of the container and compromise the host environment.

Vulnerability Details

CVE-ID: CVE-2026-47135

Affected Software: vm2 (Node.js sandbox)

Affected Versions: vm2, npm, <= 3.11.3

Vulnerability: This is a sandbox escape vulnerability involving the manipulation of host-side behavior. By exploiting an incomplete override of the global Symbol.for function and a flaw in the proxy-based bridge's write-trap handlers, an attacker can execute code outside the intended sandbox environment.

Business Impact

Successful exploitation allows an attacker to achieve host-level code execution, effectively bypassing the security boundary of the Node.js sandbox. Given the CVSS score of 8.7, this represents a significant risk to data integrity and system confidentiality. Compromise of the host environment can lead to unauthorized access to sensitive application data and the potential for full system takeover.

Remediation Plan

Immediate Action: Upgrade the vm2 library to version 3.11.4 or later immediately.

Proactive Monitoring: Monitor server logs for unexpected process execution or attempts to access host-level system resources originating from sandboxed processes.

Compensating Controls: Implement strict resource constraints and process isolation (e.g., cgroups or containerization) to limit the impact if the sandbox is breached.

Exploitation Status

Public Exploit Available: true

Analyst Notes: As of June 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the availability of public exploit code and the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The severity of this sandbox escape necessitates an immediate update to version 3.11.4. Security teams must prioritize this patch to prevent unauthorized host-level access, as the existence of public exploit code significantly lowers the barrier to entry for potential attackers.

Description Summary:
A sandbox escape vulnerability in vm2 allows unauthenticated attackers to execute arbitrary code on the host system via prototype mutation.

Executive Summary:
A critical sandbox escape vulnerability in vm2 (versions <= 3.11.3) allows unauthenticated attackers to achieve arbitrary code execution on the host machine.

Vulnerability Details

CVE-ID: CVE-2026-47131

Affected Software: vm2 (vm2)

Affected Versions: vm2 prior to version 3.11.4, or versions <= 3.11.3.

Vulnerability: This is a sandbox escape vulnerability where unauthenticated attackers can leverage host-side object prototype mutation. By combining specific Buffer function calls with Node.js error types, an attacker can obtain the host's TypeError constructor to break out of the sandbox environment.

Business Impact

The exploitation of this vulnerability results in a complete compromise of the host system, allowing for unauthorized code execution. Given the critical CVSS score of 10.0, this represents a severe risk to data confidentiality, integrity, and availability, potentially leading to full system takeover and lateral movement within the network.

Remediation Plan

Immediate Action: Upgrade vm2 to version 3.11.4 or higher immediately to apply the patch that prevents improper access to host-side constructors.

Proactive Monitoring: Monitor application logs for unusual sandbox behavior, including attempts to access sensitive Node.js internal objects or unexpected prototype modifications.

Compensating Controls: Implement strict environment egress filtering and run sandboxed processes with the least privilege necessary to limit the impact of a potential breakout.

Exploitation Status

Public Exploit Available: True

Analyst Notes: As of Jun 12, 2026, public exploit code is available for this vulnerability. Given the ease of achieving arbitrary code execution, the potential for exploitation is extremely high.

Analyst Recommendation

This vulnerability represents a critical risk to any infrastructure utilizing the vm2 library. Administrators must prioritize updating to version 3.11.4 immediately, as the availability of public exploits significantly lowers the barrier for attackers to compromise host systems.

Description Summary:
The vm2 sandbox library for Node.js is vulnerable to sandbox escape via async generator manipulation, allowing arbitrary command execution.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library allows attackers to execute arbitrary commands by manipulating async generators.

Vulnerability Details

CVE-ID: CVE-2026-45411

Affected Software: Node.js vm2

Affected Versions: Prior to 3.11.3

Vulnerability: The vulnerability exists in how the sandbox handles exceptions within async generators. By exploiting the yield* expression and the return function, an unauthenticated attacker can catch host exceptions and execute arbitrary code outside the intended sandbox boundary.

Business Impact

The CVSS score of 9.8 reflects the extreme severity of this flaw. Successful exploitation grants an attacker full control over the host system, which can result in complete data exfiltration, unauthorized modification of system resources, and total loss of confidentiality and availability for the affected application.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.3 or later immediately.

Proactive Monitoring: Review application logs for abnormal error patterns related to async generator execution or unexpected system-level command calls.

Compensating Controls: Deploy Web Application Firewalls (WAF) or Runtime Application Self-Protection (RASP) tools capable of detecting anomalous script execution patterns in Node.js environments.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability provides a direct pathway for attackers to bypass security boundaries. Immediate patching is mandatory to secure the host environment, and developers should verify that no secondary mechanisms exist that could allow similar manipulation of the sandbox.

Description Summary:
The vm2 sandbox library for Node.js is vulnerable to sandbox escape, potentially allowing arbitrary command execution on the host system.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library for Node.js poses a significant risk of arbitrary code execution on host systems.

Vulnerability Details

CVE-ID: CVE-2026-44009

Affected Software: Node.js vm2

Affected Versions: Prior to 3.11.2

Vulnerability: This is a sandbox breakout vulnerability that allows an attacker to bypass the isolation mechanisms of the vm2 environment, leading to full system compromise. The vulnerability can be triggered by an unauthenticated attacker providing malicious input to the sandbox.

Business Impact

With a CVSS score of 9.8, this vulnerability represents a critical risk to business continuity and data integrity. Successful exploitation allows an attacker to break out of the intended sandbox environment and execute arbitrary commands on the underlying host, potentially leading to unauthorized access to sensitive data, system takeover, or the deployment of ransomware.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.2 or later immediately to apply the necessary security patches.

Proactive Monitoring: Monitor server logs for unusual process execution or attempts to access restricted file paths originating from Node.js applications.

Compensating Controls: Implement strict containerization and principle-of-least-privilege policies for all Node.js environments to limit the blast radius if the sandbox is compromised.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical nature of sandbox escapes, organizations utilizing vm2 must prioritize this update. Ensure that all dependencies are audited and that the patching process is completed across all production and development environments to prevent potential host-level exploitation.

Description Summary:
The vm2 sandbox for Node.js is vulnerable to an array species batch neutralization flaw, allowing attackers to escape the sandbox and execute arbitrary commands.

Executive Summary:
A critical sandbox escape in the vm2 library allows attackers to access host functions and execute arbitrary commands on the host system.

Vulnerability Details

CVE-ID: CVE-2026-44008

Affected Software: Node.js vm2

Affected Versions: Prior to 3.11.2

Vulnerability: The neutralizeArraySpeciesBatch method improperly handles objects across the sandbox boundary. Attackers can leverage this to retrieve host objects, including the host Function object, and escape the sandbox.

Business Impact

The CVSS score of 9.8 underscores the severe risk of host system compromise. Successful exploitation grants the attacker the ability to escape the sandbox and execute arbitrary commands on the underlying host, leading to full system takeover.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.2 or later immediately.

Proactive Monitoring: Monitor for unexpected system-level processes or unusual file system activity originating from the Node.js application.

Compensating Controls: Enforce strict process-level security, such as using seccomp profiles to block unauthorized system calls if a sandbox escape occurs.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the persistent issues with vm2 sandbox escapes, users should ensure they are on the latest version (3.11.2+) and consider if the use of a sandbox is sufficient for their security requirements or if additional defense-in-depth measures are needed.

Description Summary:
The vm2 sandbox for Node.js is vulnerable to prototype access, allowing attackers to reach arbitrary prototypes and escape the sandbox.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library allows attackers to access arbitrary prototypes and gain control over the host environment.

Vulnerability Details

CVE-ID: CVE-2026-44006

Affected Software: Node.js vm2

Affected Versions: Prior to 3.11.0

Vulnerability: The sandbox fails to restrict access to BaseHandler.getPrototypeOf. By reaching this handler, an attacker can retrieve arbitrary prototypes, enabling a sandbox escape and subsequent host-level execution.

Business Impact

The CVSS score of 10.0 confirms this as a critical risk. Successful exploitation grants the attacker full control over the host system, potentially leading to unauthorized data access, service disruption, and compromise of the entire Node.js application environment.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.0 or later immediately to patch the prototype access handler.

Proactive Monitoring: Monitor for unusual JavaScript execution patterns or attempts to reflect on object prototypes within the application.

Compensating Controls: Implement strict resource limits and process isolation for any Node.js application that processes untrusted code.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability is a severe threat to any system relying on vm2 for isolation. Upgrading to the latest version is the only effective mitigation and must be performed immediately.

Description Summary:
The vm2 sandbox for Node.js is vulnerable to prototype pollution, allowing sandboxed code to mutate host-realm objects and escape the environment.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library allows attackers to mutate host-realm objects and execute code outside the intended environment.

Vulnerability Details

CVE-ID: CVE-2026-44005

Affected Software: Node.js vm2

Affected Versions: 3.9.6 to 3.10.5

Vulnerability: The library incorrectly exposes mutable proxies for host-realm intrinsic prototypes. This allows sandboxed JavaScript to modify critical objects such as Object.prototype, facilitating a sandbox escape.

Business Impact

With a CVSS score of 10.0, this vulnerability represents the highest level of risk. Exploitation allows an attacker to break out of the Node.js sandbox, leading to arbitrary code execution on the underlying host system, full server compromise, and potential lateral movement within the network.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.0 or later immediately to address the proxy exposure issue.

Proactive Monitoring: Monitor for anomalous process behavior or unexpected file system modifications originating from Node.js applications utilizing the vm2 library.

Compensating Controls: Ensure that Node.js applications are running with the principle of least privilege, utilizing containerization or restricted service accounts to limit the blast radius of a potential escape.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

Given the critical nature of this sandbox escape, users must upgrade to version 3.11.0 immediately. Organizations should conduct a thorough audit of all Node.js applications relying on vm2 for isolation to ensure they are updated and secure.

Description Summary:
The vm2 sandbox environment is vulnerable to an uncaught exception flaw, which can be leveraged to cause a denial-of-service or potentially escape the sandbox.

Executive Summary:
An uncaught exception vulnerability in the vm2 sandbox environment allows unauthenticated attackers to cause service instability and potential security bypasses.

Vulnerability Details

CVE-ID: CVE-2026-44001

Affected Software: patriksimek vm2

Affected Versions: < 3.11.0

Vulnerability: The vulnerability (CWE-248) involves an uncaught exception that can be triggered by an attacker. This flaw allows for escape from the sandbox environment or can lead to a denial-of-service condition affecting the Node.js runtime.

Business Impact

A successful exploit could crash the application or allow an attacker to execute code outside of the restricted sandbox, leading to a complete compromise of the host environment. Given the CVSS score of 8.6, this vulnerability poses a severe risk to any application relying on vm2 for secure code execution.

Remediation Plan

Immediate Action: Upgrade the vm2 package to version 3.11.0 or higher.

Proactive Monitoring: Monitor application stability and error logs for recurring uncaught exceptions or unexpected process terminations that may indicate exploitation attempts.

Compensating Controls: If upgrading is not immediately possible, consider moving away from vm2 to more modern, actively maintained isolation alternatives, as the sandbox model itself may be fragile.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of May 14, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The vulnerability is highly exploitable due to the nature of sandbox escapes.

Analyst Recommendation

Upgrade to version 3.11.0 immediately to resolve the sandbox escape risk. Given the potential for complete host compromise, this update should be treated with the highest urgency in your security maintenance schedule.

Description Summary:
The vm2 sandbox for Node.js contains a bypass in its builtin allowlist, enabling unauthorized access to restricted modules and arbitrary code execution.

Executive Summary:
A critical sandbox bypass in the vm2 library allows attackers to load forbidden modules and execute arbitrary code on the host system.

Vulnerability Details

CVE-ID: CVE-2026-43999

Affected Software: Node.js vm2

Affected Versions: Prior to 3.11.0

Vulnerability: The sandbox's builtin allowlist can be bypassed by abusing the module builtin. This allows sandboxed code to access Node.js Module._load() to load restricted modules like child_process, resulting in host-level code execution.

Business Impact

The CVSS score of 9.9 highlights the extreme severity of this flaw. By achieving remote code execution outside the sandbox, an attacker can gain full control over the host, leading to data loss, system destruction, or persistent unauthorized access.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.0 or later to ensure the builtin allowlist is properly enforced.

Proactive Monitoring: Audit Node.js application logs for attempts to load sensitive modules such as child_process, fs, or net from within sandboxed environments.

Compensating Controls: Use strict environment variable configurations to restrict the capabilities of the Node.js process and prevent the spawning of child processes.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This is a critical vulnerability that effectively nullifies the isolation provided by vm2. It is imperative to update the library immediately and review all code that relies on this sandbox for security purposes.

Description Summary:
The vm2 Node.js sandbox environment is vulnerable to improper link resolution, allowing attackers to bypass sandbox restrictions via link following.

Executive Summary:
A high-severity sandbox escape vulnerability in the vm2 library allows authenticated attackers to execute arbitrary code with host-level permissions.

Vulnerability Details

CVE-ID: CVE-2026-43998

Affected Software: Patriksimek vm2

Affected Versions: 3.10.5

Vulnerability: This vulnerability is caused by improper link resolution before file access (CWE-59), which permits an attacker with low-level privileges to bypass the sandbox environment and interact with the host filesystem.

Business Impact

The ability to escape a sandboxed environment represents a critical security failure, as it allows unauthorized access to the underlying host system. Given the CVSS score of 8.5, this flaw poses a significant risk of full system compromise, data exfiltration, or lateral movement within the network.

Remediation Plan

Immediate Action: Update the vm2 package to version 3.11.0 or later as specified by the OSV advisory.

Proactive Monitoring: Monitor application logs for unusual file system access patterns or attempts to traverse directories outside of the designated sandbox.

Compensating Controls: If immediate patching is not possible, implement strict filesystem permissions for the Node.js process to limit the impact of a potential escape.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of May 14, 2026, there is no confirmed active exploitation in the wild; however, per CISA's SSVC assessment a proof-of-concept exists, so exploitation risk should be treated as credible. The complexity of the sandbox escape makes it a targeted vector for sophisticated actors.

Analyst Recommendation

Organizations utilizing the vm2 library must prioritize updating to version 3.11.0 immediately. The presence of a proof-of-concept combined with the potential for total system impact necessitates rapid remediation to prevent host-level exploitation.

Description Summary:
The vm2 sandbox for Node.js is vulnerable to a host object escape, allowing attackers to access the host environment by leveraging native symbols.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library allows attackers to access host objects and bypass security restrictions.

Vulnerability Details

CVE-ID: CVE-2026-43997

Affected Software: Node.js vm2

Affected Versions: Prior to 3.11.0

Vulnerability: The sandbox fails to properly restrict access to the host Object. Attackers can use HostObject.getOwnPropertySymbols to obtain sensitive references, enabling a full escape from the sandbox.

Business Impact

A CVSS score of 10.0 signifies an extremely high risk of compromise. Successful exploitation grants the attacker the ability to interact with the host environment, leading to full system control, sensitive data exposure, and potential compromise of the underlying infrastructure.

Remediation Plan

Immediate Action: Update the vm2 library to version 3.11.0 or later immediately.

Proactive Monitoring: Monitor system logs for unusual Node.js activity that deviates from standard application behavior, specifically looking for attempts to access non-sandboxed modules or system functions.

Compensating Controls: Employ robust system-level isolation, such as running Node.js processes within hardened containers or gVisor, to minimize the impact if the sandbox is breached.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of May 13, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability represents a severe security failure in the isolation mechanism. All systems utilizing versions of vm2 prior to 3.11.0 must be patched immediately to prevent complete host system compromise.

Description Summary:
A full sandbox escape vulnerability in vm2 version 3.10.4 allows attackers to access the host process object and execute arbitrary host commands.

Executive Summary:
A critical sandbox escape vulnerability in vm2 allows attackers to gain access to the host process object and execute arbitrary commands on the system.

Vulnerability Details

CVE-ID: CVE-2026-26956

Affected Software: vm2 (Node.js)

Affected Versions: 3.10.4

Vulnerability: This is a full sandbox escape that allows code running within VM.run() to obtain the host process object. With this access, an attacker can execute arbitrary commands on the host system without any cooperation from the host itself.

Business Impact

The CVSS score of 9.8 indicates that this is a critical vulnerability. An attacker can achieve complete system compromise, bypassing all intended restrictions of the vm2 sandbox, potentially leading to unauthorized data access and system manipulation.

Remediation Plan

Immediate Action: Upgrade vm2 to version 3.10.5 or later to resolve the sandbox escape.

Proactive Monitoring: Monitor for suspicious process activity or unauthorized modifications to the host system by the Node.js application.

Compensating Controls: Utilize kernel-level security features to limit the process's capabilities and prevent the exploitation of process objects.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability is exceptionally dangerous as it grants direct access to the host process. Immediate patching is required. Organizations should treat this as a high-priority security update and review their application's dependency tree to ensure the patch is correctly applied.

Description Summary:
A vulnerability involving SuppressedError in the vm2 library allows attackers to escape the sandbox and execute arbitrary code on the host system.

Executive Summary:
A critical sandbox breakout vulnerability in vm2 allows attackers to leverage SuppressedError to execute arbitrary code on the host.

Vulnerability Details

CVE-ID: CVE-2026-26332

Affected Software: vm2 (Node.js)

Affected Versions: Prior to 3.11.0

Vulnerability: The SuppressedError object in the vm2 environment can be manipulated to facilitate a sandbox escape. By exploiting this, an attacker can move outside the restricted environment and execute arbitrary code on the host.

Business Impact

A CVSS score of 9.8 reflects the high severity of this sandbox escape. Exploitation could allow an attacker to gain full control over the host system, leading to complete data compromise and potential disruption of critical business processes.

Remediation Plan

Immediate Action: Update the vm2 dependency to version 3.11.0 or later to address this breakout vulnerability.

Proactive Monitoring: Monitor application logs for unexpected error patterns or unusual code execution sequences.

Compensating Controls: Run the Node.js application with minimal system privileges and use containerization to restrict access to the underlying host resources.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The continued discovery of sandbox escapes in vm2 underscores the difficulty of maintaining a secure JavaScript sandbox. Updating the library is mandatory, but organizations should also assess the necessity of running untrusted code and consider more secure architectural alternatives.

Description Summary:
A sandbox breakout vulnerability in the vm2 library's inspect function allows attackers to escape the sandbox and execute arbitrary commands on the host.

Executive Summary:
A critical sandbox breakout vulnerability in the vm2 library's inspect function allows attackers to escape the sandbox and execute arbitrary commands on the host.

Vulnerability Details

CVE-ID: CVE-2026-24781

Affected Software: vm2 (Node.js)

Affected Versions: Prior to 3.11.0

Vulnerability: The inspect function in vm2 allows an attacker to manipulate objects in a way that escapes the sandbox environment. This facilitates arbitrary code execution on the host system running the Node.js environment.

Business Impact

With a CVSS score of 9.8, this vulnerability poses a severe threat. Successful exploitation grants the attacker the same permissions as the Node.js process, which can lead to data exfiltration, system destruction, or unauthorized lateral movement within the network.

Remediation Plan

Immediate Action: Update the vm2 dependency to version 3.11.0 or later to mitigate this sandbox breakout vector.

Proactive Monitoring: Monitor for anomalous usage of the inspect function or unexpected object manipulation patterns within the application.

Compensating Controls: Implement robust ingress and egress filtering on the host system to prevent unauthorized command-and-control communication in the event of an escape.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The frequency of sandbox escape vulnerabilities in vm2 suggests that it is not a secure solution for running untrusted code. Organizations are strongly advised to update the library and investigate safer alternatives for code isolation if the requirement for running untrusted code persists.

Description Summary:
An insufficient patch for a previous vm2 vulnerability allows attackers to bypass security measures and perform a sandbox breakout for arbitrary code execution.

Executive Summary:
A critical sandbox breakout vulnerability in vm2 allows attackers to bypass previous security patches and execute arbitrary code on the host system.

Vulnerability Details

CVE-ID: CVE-2026-24120

Affected Software: vm2 (Node.js)

Affected Versions: Prior to 3.10.5

Vulnerability: This issue is a bypass of the fix for CVE-2023-37466. It allows an attacker to craft code that circumvents existing sandbox protections, enabling the execution of arbitrary commands on the host OS.

Business Impact

The CVSS score of 9.8 confirms the severity of this sandbox escape. By exploiting this, an attacker can move from a contained environment to the host system, leading to complete system compromise, data theft, or the installation of persistent malware.

Remediation Plan

Immediate Action: Update the vm2 dependency to version 3.10.5 or later to apply the necessary security fixes.

Proactive Monitoring: Monitor for unexpected shell commands or suspicious network connections initiated by the Node.js process.

Compensating Controls: Use strict system-level controls, such as SELinux or AppArmor, to restrict what the Node.js process can execute on the host.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

This vulnerability demonstrates the persistence of security flaws in complex sandbox libraries. Developers must prioritize updating dependencies and should evaluate if their application architecture can be modified to avoid executing untrusted code within a Node.js-based sandbox.

Description Summary:
A sandbox breakout vulnerability in the Node.js vm2 library allows attackers to escape the sandbox and execute arbitrary commands on the host system.

Executive Summary:
A critical sandbox breakout vulnerability in vm2 allows attackers to escape the virtual environment and achieve arbitrary command execution on the host.

Vulnerability Details

CVE-ID: CVE-2026-24118

Affected Software: vm2 (Node.js)

Affected Versions: Prior to 3.11.0

Vulnerability: The vulnerability allows an attacker to break out of the vm2 sandbox environment. By crafting specific code, an attacker can bypass security restrictions and execute arbitrary commands directly on the host system running the Node.js application.

Business Impact

With a CVSS score of 9.8, this flaw represents a complete failure of the isolation mechanism. If a Node.js application uses vm2 to process untrusted input, an attacker can gain full access to the underlying server, potentially compromising all data and services hosted on that machine.

Remediation Plan

Immediate Action: Update the vm2 dependency to version 3.11.0 or later immediately.

Proactive Monitoring: Review application logs for unusual child process creation or unauthorized file system access originating from the Node.js application.

Compensating Controls: Run the Node.js application within a containerized environment (e.g., Docker) with restricted capabilities and no root privileges to limit the impact of a potential breakout.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of May 4, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.

Analyst Recommendation

The vm2 library is inherently difficult to secure, and this breakout vulnerability highlights the risks of relying on it for sandboxing untrusted code. Organizations must update to the latest version and consider adopting stronger isolation methods, such as hardware-based virtualization or separate, hardened processes.

Description Summary:
The vm2 sandbox for Node.js fails to sanitize global Promise callbacks, allowing unauthenticated attackers to escape the sandbox and execute arbitrary code.

Executive Summary:
A critical sandbox escape vulnerability in the vm2 library allows unauthenticated remote attackers to achieve full code execution on the underlying host system.

Vulnerability Details

CVE-ID: CVE-2026-22709

Affected Software: patriksimek vm2

Affected Versions: < 3.10.2

Vulnerability: This vulnerability involves a failure in the sanitization of globalPromise.prototype.then and catch callbacks within the vm2 sandbox environment. Because the sandbox fails to properly restrict these global objects, an unauthenticated attacker can bypass isolation mechanisms to execute arbitrary code.

Business Impact

The ability to escape a sandbox and execute arbitrary code represents a total compromise of the affected Node.js application and its host environment. Given the CVSS score of 9.8, this flaw poses an extreme risk of data exfiltration, service disruption, and lateral movement within the network. Organizations relying on vm2 for executing untrusted code are at high risk of complete system takeover.

Remediation Plan

Immediate Action: Update the vm2 package to version 3.10.2 or later immediately to apply the necessary sanitization fixes.

Proactive Monitoring: Monitor server logs for unexpected process execution, unusual outbound network connections, or attempts to access restricted file system paths originating from the Node.js application.

Compensating Controls: While a WAF may not prevent sandbox escapes, strict environment hardening and the principle of least privilege should be applied to the user account running the Node.js process to limit the impact of potential code execution.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Jan 26, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous because it allows a direct escape from a security boundary intended to isolate untrusted code.

Analyst Recommendation

The severity of this vulnerability cannot be overstated, as it negates the primary security function of the vm2 library. Administrators must prioritize updating all instances of vm2 to version 3.10.2 or later. Given the ease of exploitability and the potential for total system compromise, immediate remediation is required to maintain the integrity and security of the hosting infrastructure.