Analyst readout for executives and security teams
Plain-English summary
This Chrome flaw could let an attacker break out of the browser sandbox after first compromising Chrome’s renderer process. It requires user interaction with crafted HTML and has high impact because confidentiality, integrity, and availability are all rated high.
Executive priority
Treat this as a high-priority browser update. The exploit chain has prerequisites, but sandbox escape impact is serious for endpoints that handle untrusted web content.
Technical view
CVE-2026-9975 is an out-of-bounds read/write in ANGLE in Google Chrome before 148.0.7778.216. The CVSS 3.1 score is 8.3 with network attack vector, high attack complexity, required user interaction, changed scope, and high CIA impact.
Likely exposure
Organizations with Google Chrome versions prior to 148.0.7778.216 are the relevant exposure group. The provided sources do not identify other affected products or platforms.
Exploitation context
The source says exploitation requires a compromised renderer process and a crafted HTML page, potentially enabling sandbox escape. CISA KEV status is false in the bundle, and no cited source states active exploitation.
Researcher notes
Public technical detail is limited. The Chromium issue link may provide restricted or evolving details, so validation should focus on version exposure and advisory tracking rather than exploit reproduction.
Mitigation direction
- Update Google Chrome to 148.0.7778.216 or later.
- Verify enterprise Chrome auto-update policies are functioning.
- Prioritize devices that browse untrusted websites or email links.
- Monitor Google Chrome release notes for revised guidance.
- Check vendor guidance if update timing or platform coverage is unclear.
Validation and detection
- Inventory Chrome versions across managed endpoints.
- Flag any Chrome installation below 148.0.7778.216.
- Confirm update policy compliance after patch rollout.
- Review the Chrome release advisory for any changed scope.
- Track KEV status for future exploitation evidence.
Public sources used
Based on public source material and reviewed before publication.
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-125: 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-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.
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-9975 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
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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
1 official scoreWe 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:H/PR:N/UI:R/S:C/C:H/I:H/A:H 1.6 6 CISA-ADP Vulnerability scoring details
Base CVSS 3.1 score
8.3 HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html CVE reference, Chrome
- https://issues.chromium.org/issues/511719039 CVE reference, Chrome
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.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
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.