Is CVE-2026-44008 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44008 being exploited in the wild.

How severe is CVE-2026-44008?

Critical severity, with a CVSS score of 9.8, published 13 May 2026.

Which products and versions are affected?

vm2 (npm) <= 3.11.1, SEMVER:introduced=0,fixed=3.11.2; Red Hat Self-service automation portal 2.

Is there a fix for CVE-2026-44008?

Yes. vm2 (npm): upgrade to 3.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44008 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-44008?

Check whether you run vm2 (npm) or Red Hat Self-service automation portal at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44008: patriksimek vm2 sandbox escape in neutralizeArraySpeciesBatch

Q: Which products and versions are affected?

vm2 (npm) <= 3.11.1, SEMVER:introduced=0,fixed=3.11.2; Red Hat Self-service automation portal 2.

Q: Is there a fix for CVE-2026-44008?

Yes. vm2 (npm): upgrade to 3.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44008 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-44008?

Check whether you run vm2 (npm) or Red Hat Self-service automation portal at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44008 · Severity: critical · CVSS 9.8 · Published 2026-05-13

vm2 is a popular software library used to run untrusted code in a secure, isolated 'sandbox' environment. A critical flaw allows an attacker to bypass these security restrictions and gain full control over the underlying server. This could lead to complete system takeover, data theft, or the installation of malicious software.

Technologies: vm2 (npm), Red Hat Self-service automation portal. Vendors: npm, Red Hat.

Quick answers

Is CVE-2026-44008 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44008 being exploited in the wild.
How severe is CVE-2026-44008?: Critical severity, with a CVSS score of 9.8, published 13 May 2026.
Which products and versions are affected?: vm2 (npm) <= 3.11.1, SEMVER:introduced=0,fixed=3.11.2; Red Hat Self-service automation portal 2.
Is there a fix for CVE-2026-44008?: Yes. vm2 (npm): upgrade to 3.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44008 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-44008?: Check whether you run vm2 (npm) or Red Hat Self-service automation portal at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

vm2 (npm): upgrade to 3.11.2 or later
```
npm install vm2@3.11.2
```

Technical details

A sandbox escape vulnerability exists in vm2 due to insufficient isolation in the 'neutralizeArraySpeciesBatch' method. The vulnerability arises because the method can be tricked into invoking getters on the host-side array prototype when processing objects from the sandbox. By defining a custom getter on the Array prototype, an attacker can leak host-side objects, including the host 'Function' object, into the sandbox environment. This allows for a complete breakout, enabling remote code execution (RCE) on the host system. The issue is fixed in version 3.11.2.

Affected products

patriksimek vm2 < 3.11.2
Red Hat Self-service automation portal 2 2

Identifiers

CVE-2026-44008
GHSA-9qj6-qjgg-37qq

Timeline

2026-05-03: advisory: Original GitHub advisory published by maintainer
2026-05-13: disclosed: NVD publication date
2026-05-13: patched: Fix confirmed available in version 3.11.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.