Security readout for executives and security teams
Plain-English summary
Applications using vm2 before 3.11.0 may let untrusted sandboxed code consume enough host memory to crash the Node.js process. One request may cause an outage, and vm2's execution timeout does not stop the allocation. The supplied sources describe availability impact, not data theft or modification.
Executive priority
Treat this as a high-priority availability issue for services executing untrusted code with affected vm2 versions. Accelerate upgrade and deployment verification for externally reachable workloads. The urgency is lower where vm2 is absent or untrusted code cannot reach the sandbox, but dependency evidence should confirm that conclusion.
Technical view
Sandboxed code can request an arbitrary allocation through Buffer.alloc(). This synchronous native operation allocates memory on the host heap and cannot be interrupted by vm2's timeout. Memory exhaustion can terminate the process with a heap-limit fatal error. The issue is classified as CWE-1285 and CWE-770 and fixed in vm2 3.11.0.
Likely exposure
Exposure is most likely where an application runs attacker-controlled or otherwise untrusted JavaScript through vm2 versions below 3.11.0. Risk depends on whether users can reach that execution path and invoke Buffer.alloc(). Systems without vm2, using 3.11.0 or later, or not processing untrusted code are not identified as affected.
Exploitation context
The CVSS 3.1 score is 8.6, reflecting remotely reachable, low-complexity availability impact without required privileges or user interaction. The bundle states that one request can crash the process. It does not provide evidence of active exploitation, and the CVE is not identified as present in KEV.
Researcher notes
The security boundary fails through resource exhaustion rather than sandbox escape or code execution. The important mechanism is that Buffer.alloc() enters synchronous C++ code, bypassing the timeout's ability to interrupt execution. Scope and practical blast radius depend on process supervision, workload placement, and whether the affected process shares resources, but those deployment details are not established by the sources.
Mitigation direction
- Upgrade vm2 to version 3.11.0 or later.
- Confirm lockfiles and deployed artifacts resolve the corrected version.
- Review the GitHub and Red Hat advisories for environment-specific guidance.
- Prioritize internet-facing services that execute user-supplied JavaScript.
Validation and detection
- Inventory direct and transitive vm2 dependencies across deployed services.
- Verify the effective runtime version is 3.11.0 or later.
- Identify endpoints or jobs that pass untrusted code into vm2.
- Review monitoring for heap-limit crashes and unexplained process restarts.
- Use safe staging validation; do not intentionally exhaust production memory.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-1285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-44004 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H3.94redhat-SADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_MVulnerability scoring details
Base CVSS 3.1 score
8.6HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-13T18:01:38.304Z: Reported to Red Hat.
- 2026-05-13T17:31:16.281Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-6785-pvv7-mvg7CVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-44004CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2477195CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44004.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:50850CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Validation of Specified Index, Position, or Offset in Input
Improper Validation of Specified Index, Position, or Offset in Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.