Security readout for executives and security teams
Plain-English summary
Applications using vm2 to run untrusted JavaScript may not be safely isolated. An attacker able to submit code to a vulnerable sandbox could escape it and execute commands on the host, potentially compromising data, workloads, and service availability. vm2 versions before 3.11.3 are affected.
Executive priority
Prioritize immediate remediation for internet-accessible or multi-tenant systems that run untrusted JavaScript through vm2. The vulnerability crosses a security boundary and can lead to full host-level confidentiality, integrity, and availability impact. Lower-access environments still require prompt inventory and upgrade.
Technical view
An async-generator yield* edge case can expose a host exception to sandboxed code. Closing the generator through its return function causes a value to be awaited; exceptions from its then call can reach the yield* iterator, enabling sandbox escape and arbitrary host command execution. The issue maps to CWE-237 and CWE-668.
Likely exposure
Exposure is most likely where vm2 earlier than 3.11.3 executes attacker-controlled or otherwise untrusted JavaScript. Risk depends on whether users can reach that execution path and on the privileges and network access of the hosting Node.js process. Presence of vm2 alone does not prove exploitability.
Exploitation context
The supplied record assigns CVSS 9.8 with network access, low complexity, no privileges, and no user interaction. However, KEV is false, and the supplied sources do not establish active exploitation. Treat public-facing untrusted-code services as urgent without claiming attacks are occurring.
Researcher notes
The decisive exposure condition is attacker influence over code executed inside vulnerable vm2. Assess wrappers, job processors, plugin systems, and indirect dependency use, but do not assume every installation is reachable. The provided evidence names 3.11.3 as the fixed version; it provides no basis for claiming exploitation in the wild.
Mitigation direction
- Upgrade vm2 to version 3.11.3 or later.
- Identify and update applications carrying vulnerable transitive vm2 dependencies.
- Redeploy or restart affected workloads so the corrected dependency is active.
- Until upgraded, suspend untrusted-code execution and consult the vendor advisory.
Validation and detection
- Confirm production dependency inventories resolve vm2 to version 3.11.3 or later.
- Map every input path that can submit code to a vm2 sandbox.
- Verify rebuilt workloads no longer contain an older bundled or cached vm2 copy.
- Review sandbox-host telemetry for unexpected processes, network activity, or filesystem changes.
- Test isolation safely in a non-production environment without weaponized payloads.
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-237: 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-45411 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:02:31.159Z: Reported to Red Hat.
- 2026-05-13T17:38:38.311Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-248r-7h7q-cr24CVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-45411CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2477210CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45411.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 Handling of Structural Elements
Improper Handling of Structural Elements 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.