Is CVE-2026-44006 exploited in the wild?

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

How severe is CVE-2026-44006?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-44006?

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

How is CVE-2026-44006 attacked?

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

Am I affected by CVE-2026-44006?

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-44006: patriksimek vm2 sandbox escape via arbitrary prototype access

Q: Which products and versions are affected?

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

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

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

Q: How is CVE-2026-44006 attacked?

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

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

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-44006 · Severity: critical · CVSS 10 · Published 2026-05-13

vm2 is a popular software library used to safely run untrusted code in an isolated 'sandbox' environment. A critical security flaw allows an attacker to break out of this isolation and execute commands directly on the underlying server. This could lead to a complete system takeover, unauthorized data access, and disruption of services.

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

Quick answers

Is CVE-2026-44006 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44006 being exploited in the wild.
How severe is CVE-2026-44006?: Critical severity, with a CVSS score of 10, published 13 May 2026.
Which products and versions are affected?: vm2 (npm) <= 3.10.5, SEMVER:introduced=0,fixed=3.11.0; Red Hat Self-service automation portal 2.
Is there a fix for CVE-2026-44006?: Yes. vm2 (npm): upgrade to 3.11.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44006 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-44006?: 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.0 or later
```
npm install vm2@3.11.0
```

Technical details

A sandbox escape vulnerability exists in vm2 due to improper control of dynamically-identified variables. Specifically, sandboxed code can reach the 'BaseHandler.getPrototypeOf' method within 'lib/bridge.js', which allows an attacker to retrieve arbitrary prototypes from the host environment. By leveraging these prototypes, an attacker can gain access to host-level constructors (such as 'process') and execute arbitrary system commands. This bypasses the sandbox security boundary entirely. The vulnerability is fixed in version 3.11.0.

Affected products

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

Identifiers

CVE-2026-44006
GHSA-qcp4-v2jj-fjx8

Timeline

2026-05-01: advisory: Original GitHub security advisory published by maintainer
2026-05-13: disclosed: CVE-2026-44006 published to NVD
2026-05-13: patched: Fix released in version 3.11.0

References

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