Security readout for executives and security teams
Plain-English summary
CVE-2026-44009 affects the Node.js vm2 sandbox before version 3.11.2. The issue can allow sandbox breakout, meaning code intended to be contained may escape those limits. Treat this as critical where vm2 runs untrusted or user-controlled JavaScript.
Executive priority
High priority for any service using vm2 to run untrusted code. The business risk is sandbox escape from a component specifically trusted to contain execution. Prioritize remediation by internet exposure and whether attackers can supply code or scripts.
Technical view
The sources identify a vm2 sandbox breakout involving a null-prototype exception. Affected versions are vm2 before 3.11.2. CVSS 3.1 is 9.8, with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in Node.js services that depend on vm2 < 3.11.2 and use it to execute untrusted, tenant-supplied, plugin, rule, or script code.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates potentially remote, unauthenticated exploitation if an attacker can reach application functionality that invokes vulnerable vm2 execution.
Researcher notes
Public evidence in the bundle is sparse: it names the class, affected range, fix version, CWE, and CVSS, but not detailed root cause or exploitation evidence. Do not assume broader product impact beyond vm2 < 3.11.2 without local dependency confirmation.
Mitigation direction
- Upgrade vm2 to version 3.11.2 or later.
- Inventory direct and transitive vm2 dependencies across all Node.js projects.
- Prioritize systems executing untrusted or user-controlled JavaScript.
- If immediate upgrade is blocked, disable or isolate vm2-backed code execution.
- Monitor the GitHub advisory and vendor guidance for updated instructions.
Validation and detection
- Check package manifests, lockfiles, and SBOMs for vm2 versions below 3.11.2.
- Confirm deployed artifacts do not bundle vulnerable vm2 versions.
- Map public or tenant-facing paths that invoke vm2 execution.
- Verify dependency scanners flag and clear CVE-2026-44009 after remediation.
- Review Red Hat status if consuming affected downstream packages.
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-653: 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-668: 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-44009 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:U/C:H/I:H/A:H3.95.9GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:02.062Z: Reported to Red Hat.
- 2026-05-13T17:36:07.309Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-9vg3-4rfj-wgcmCVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-44009CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2477185CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44009.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
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 Isolation or Compartmentalization
Improper Isolation or Compartmentalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Exposure of Resource to Wrong Sphere
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.