Quick answers
- Is CVE-2026-44009 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44009 being exploited in the wild.
- How severe is CVE-2026-44009?
- Critical severity, with a CVSS score of 9.8, published 13 May 2026.
- Which products and versions are affected?
- vm2 (npm) < 3.11.2, SEMVER:introduced=0,fixed=3.11.2; Red Hat Self-service automation portal 2.
- Is there a fix for CVE-2026-44009?
- 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-44009 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44009?
- 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 breakout vulnerability exists in vm2 due to improper handling of exceptions with a null prototype in the handleException function. When an object with a null prototype is thrown and caught, the sandbox incorrectly assumes the exception is proxied, allowing an attacker to access the host's Function object. This bypasses the isolation layer, enabling Remote Code Execution (RCE) on the host system. The vulnerability is reachable if an attacker can provide arbitrary JavaScript to be executed within the vm2 sandbox. This 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-44009
- GHSA-9vg3-4rfj-wgcm
Timeline
- 2026-05-03: advisory: Original GitHub advisory published by patriksimek
- 2026-05-13: disclosed: CVE published to NVD
- 2026-05-13: patched: Fix released in version 3.11.2