CVE-2026-9974: Out of bounds write in GPU in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compr...
Out of bounds write in GPU 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-9974 is a high-severity Chrome GPU memory corruption flaw. A remote attacker who already compromised Chrome’s renderer could use a crafted HTML page to potentially escape the browser sandbox. That raises business urgency because sandbox escape can turn a browser compromise into broader endpoint impact.
Executive priority
Treat this as a high-priority browser patching item. It is not confirmed exploited in the provided evidence, but sandbox escape potential increases endpoint risk if paired with renderer compromise.
Technical view
The issue is an out-of-bounds write in Chrome’s GPU component, categorized as CWE-787. Sources state Chrome versions before 148.0.7778.216 are affected. CVSS 3.1 is 8.3 with network attack vector, high complexity, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations with managed or unmanaged desktop Chrome installations below 148.0.7778.216 may be exposed. The bundle identifies Google Chrome only; it does not prove impact to other Chromium-based browsers.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The attack scenario requires a crafted HTML page and prior renderer compromise, so this is not described as a one-click standalone compromise in the bundle.
Researcher notes
Evidence is limited to the CVE description, CVSS data, Chrome release reference, and Chromium issue reference. Avoid assuming exploit availability, affected downstream browsers, or detailed fixes beyond updating Chrome per vendor guidance.
Mitigation direction
Update Google Chrome to 148.0.7778.216 or later.
Review Google Chrome release guidance for any additional vendor instructions.
Prioritize managed browser update compliance across desktop fleets.
Limit exposure to untrusted browsing where rapid patching is delayed.
Validation and detection
Inventory Chrome versions across endpoints and VDI images.
Confirm all Chrome installations are at least 148.0.7778.216.
Check browser management policies for enforced automatic updates.
Track exceptions until patched or otherwise justified.
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.