Security readout for executives and security teams
Plain-English summary
Applications using vm2 before version 3.11.0 to run untrusted JavaScript may lose the isolation the sandbox is intended to provide. A successful escape could expose the host application and its data, making this an urgent issue wherever attacker-controlled code reaches vm2.
Executive priority
Treat as an emergency remediation for systems executing untrusted JavaScript through affected vm2 versions. Assign immediate ownership, identify exposed services, and upgrade promptly. Prioritization may be lower only after teams verify vm2 is absent, updated, or unreachable by untrusted input.
Technical view
CVE-2026-44006 is a vm2 sandbox escape involving access to BaseHandler.getPrototypeOf and arbitrary prototypes. The record associates it with improper sandboxed-code neutralization and code injection. Versions earlier than 3.11.0 are affected; 3.11.0 contains the fix. The supplied CVSS 3.1 score is 10.0.
Likely exposure
Highest exposure exists where a service uses vm2 below 3.11.0 to evaluate code supplied or influenced by untrusted users. Systems that do not include vm2, run 3.11.0 or later, or never pass untrusted code into it are less likely to be exposed.
Exploitation context
The supplied sources establish a critical sandbox escape but do not establish active exploitation, and the CVE is not identified as being in KEV. No conclusions about public exploit availability or observed attacks should be drawn from this bundle.
Researcher notes
The bundle identifies the vulnerable mechanism at a high level but provides insufficient detail to assess exploit reliability, environmental prerequisites beyond affected vm2 usage, or detection indicators. Validate exposure through dependency and data-flow analysis. Avoid interpreting the CVSS network vector alone as proof that every affected deployment is remotely reachable.
Mitigation direction
- Upgrade vm2 to version 3.11.0 or later.
- Prioritize internet-facing services that evaluate user-controlled JavaScript.
- Suspend untrusted-code execution where upgrading cannot be completed promptly.
- Apply relevant Red Hat updates where affected packaged components are used.
- Check vendor guidance for any additional downstream remediation requirements.
Validation and detection
- Inventory direct and transitive vm2 dependencies across applications and deployed artifacts.
- Confirm the runtime-resolved vm2 version is 3.11.0 or later.
- Identify every path where external input can reach vm2 evaluation.
- Verify updated deployments, containers, and lockfiles no longer contain affected versions.
- Review vendor advisories for product-specific applicability and update status.
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-914: 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-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-44006 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
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:C/C:H/I:H/A:H3.96GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:53.155Z: Reported to Red Hat.
- 2026-05-13T17:31:54.902Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-qcp4-v2jj-fjx8CVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-44006CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2477200CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44006.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 Control of Dynamically-Identified Variables
Improper Control of Dynamically-Identified Variables represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.