CVE-2026-9967: Out of bounds write in GPU in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentiall...
Out of bounds write in GPU in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
This Chrome flaw can let a malicious web page break out of Chrome's sandbox through the GPU component. That raises business risk because a normal browsing action could expose data or systems if users run an unpatched Chrome build.
Executive priority
Treat this as urgent browser patching. The issue has critical CVSS impact and sandbox-escape potential, but the provided evidence does not show active exploitation.
Technical view
CVE-2026-9967 is a CWE-787 out-of-bounds write in Chrome's GPU component before 148.0.7778.216. The CVSS 3.1 vector is network-based, low complexity, no privileges required, user interaction required, changed scope, with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely for desktop endpoints running Google Chrome versions earlier than 148.0.7778.216. The bundle does not identify other Chromium-based browsers or platforms, so do not assume coverage without vendor confirmation.
Exploitation context
The source states a remote attacker could potentially perform sandbox escape via a crafted HTML page. KEV is false, and the provided sources do not state active exploitation or public exploit availability.
Researcher notes
Public technical detail is limited. The Chromium issue reference may not expose full internals. Validation should focus on version state, patch deployment, and monitoring rather than exploit reproduction.
Mitigation direction
Update Google Chrome to 148.0.7778.216 or later through managed update channels.
Prioritize Chrome updates on user workstations and high-risk browsing environments.
Check Google's release guidance for any platform-specific update instructions.
Monitor CISA KEV and Google Chrome release notes for exploitation status changes.
Validation and detection
Inventory Chrome versions across managed endpoints.
Confirm no desktop Chrome install remains below 148.0.7778.216.
Verify browser update policies are active and reporting successful installs.
Review security telemetry for suspicious browser crashes or sandbox-related alerts.
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-787: 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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.