CVE-2026-9970: Use after free in WebGL in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromi...
Use after free in WebGL in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
CVE-2026-9970 is a high-severity Chrome WebGL memory-safety flaw. An attacker would need a user to open a crafted HTML page and already compromise Chrome's renderer process, but the impact could be sandbox escape, meaning stronger control beyond the browser's normal containment.
Executive priority
Treat this as a prompt browser patching item, not a confirmed emergency. The potential impact is serious, but the available evidence does not indicate active exploitation.
Technical view
The issue is a CWE-416 use-after-free in WebGL affecting Google Chrome prior to 148.0.7778.216. CVSS 3.1 is 8.3 with network attack vector, user interaction required, high attack complexity, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations with managed or unmanaged desktops running Google Chrome prior to 148.0.7778.216 are the relevant exposure. The provided sources do not name other affected products or platforms.
Exploitation context
The provided sources do not show known active exploitation, and the CVE is not marked KEV. Exploitation is described as requiring a crafted HTML page and a previously compromised renderer process.
Researcher notes
Evidence is limited to the CVE data and Google-linked references. The Chromium issue may not provide full public technical detail, so avoid assuming exploit primitives beyond use-after-free, WebGL, renderer compromise, and sandbox escape potential.
Mitigation direction
Update Google Chrome to 148.0.7778.216 or current vendor-recommended stable release.
Prioritize managed browser update enforcement for high-risk user groups.
Check Google Chrome release guidance for any additional vendor instructions.
Monitor CISA KEV and Google advisories for exploit-status changes.
Validation and detection
Inventory Chrome versions across managed endpoints.
Confirm no endpoints remain below 148.0.7778.216.
Review browser management policies for automatic update enforcement.
Track exceptions for systems unable to update promptly.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-416: 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.
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.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.