Security readout for executives and security teams
Plain-English summary
CVE-2026-26332 is a critical sandbox escape in vm2, a Node.js sandbox library. Applications using vm2 before 3.11.0 may let attacker-controlled code break out of the sandbox and run arbitrary code. The vendor advisory says the issue is fixed in 3.11.0.
Executive priority
Treat this as urgent for any service using vm2 to isolate untrusted code. Prioritize inventory and upgrade because the stated impact is arbitrary code execution from a sandbox escape.
Technical view
vm2 before 3.11.0 is affected by a SuppressedError sandbox escape leading to arbitrary code execution. The CVSS 3.1 score is 9.8 with network attack vector, low complexity, no privileges, and no user interaction. Listed weaknesses include protection mechanism failure and code injection categories.
Likely exposure
Exposure is most likely in Node.js applications that directly or transitively depend on vm2 versions below 3.11.0, especially where vm2 executes untrusted or user-controlled code.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The advisory indicates severe impact if vulnerable vm2 use is reachable, but detailed exploit conditions are not provided here.
Researcher notes
Focus on reachability and dependency provenance rather than exploit reproduction. The public bundle identifies SuppressedError as the mechanism and 3.11.0 as the fix, but does not provide evidence of exploitation in the wild or affected downstream products.
Mitigation direction
- Upgrade vm2 to version 3.11.0 or later.
- Update lockfiles and rebuild deployed artifacts using the fixed dependency.
- Identify downstream packages that bundle or pin vulnerable vm2 versions.
- Review vendor and distribution guidance for affected packaged software.
- Pause high-risk untrusted code execution until the fixed version is deployed.
Validation and detection
- Check package manifests and lockfiles for vm2 versions below 3.11.0.
- Confirm production artifacts include vm2 3.11.0 or later.
- Use dependency inventory or SBOM data to find transitive vm2 usage.
- Review code paths that execute untrusted input inside vm2.
- Track Red Hat and upstream advisory status for downstream impact.
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-693: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-26332 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:H/UI:N/S:C/C:H/I:H/A:H2.36redhat-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.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/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-04T19:02:30.129Z: Reported to Red Hat.
- 2026-05-04T16:35:52.706Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/patriksimek/vm2/security/advisories/GHSA-55hx-c926-fr95CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/patriksimek/vm2/releases/tag/v3.11.0CVE reference, GitHub_M · x_refsource_MISC
- https://access.redhat.com/security/cve/CVE-2026-26332CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2466508CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-26332.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.
Protection Mechanism Failure
Protection Mechanism Failure 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.