Quick answers
- Is CVE-2026-44004 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44004 being exploited in the wild.
- How severe is CVE-2026-44004?
- High severity, with a CVSS score of 7.5, 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-44004?
- 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-44004 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44004?
- 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 vulnerability in vm2's bridge proxy allows sandboxed code to call the native 'Buffer.alloc()' function with arbitrary size parameters. Because this is a synchronous C++ native call, it bypasses vm2's JavaScript-level timeout mechanism, which cannot interrupt the execution until the allocation completes. An attacker can trigger a massive allocation with a single request, leading to host heap exhaustion and a 'FATAL ERROR: Reached heap limit' crash. This is particularly effective in memory-constrained environments like Docker, Lambda, or Kubernetes. The issue is fixed in version 3.11.0 by validating allocation sizes.
Affected products
- patriksimek vm2 < 3.11.0
- Red Hat Self-service automation portal 2 2
Identifiers
- CVE-2026-44004
- GHSA-6785-pvv7-mvg7
Timeline
- 2026-05-01: advisory: GitHub advisory GHSA-6785-pvv7-mvg7 published
- 2026-05-13: disclosed: CVE-2026-44004 published
- 2026-05-13: patched: Fixed in version 3.11.0