Analyst readout for executives and security teams
Plain-English summary
This is a critical Chrome on Android GPU memory corruption flaw. A malicious webpage could potentially let an attacker escape Chrome's sandbox after user interaction. That raises business urgency because successful exploitation could undermine browser isolation on affected Android devices.
Executive priority
Treat as urgent for Android browser patching because it is critical, remotely reachable, and could affect sandbox isolation. There is no sourced evidence of active exploitation in the bundle, but the impact justifies accelerated update validation.
Technical view
CVE-2026-9872 is a CWE-787 out-of-bounds write in Chrome's GPU component on Android before 148.0.7778.216. The CVSS 3.1 score is 9.6 with network attack vector, low complexity, no privileges, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations with Android devices running Google Chrome versions before 148.0.7778.216 are the stated exposure. The bundle does not identify other affected products or platforms; one referenced release page title appears desktop-focused, so confirm Android channel applicability with Google guidance.
Exploitation context
The provided sources do not state active exploitation, and KEV is false. The described scenario is remote delivery through a crafted HTML page with user interaction. Public technical detail is limited, likely because Chromium issue access may be restricted.
Researcher notes
Public sources identify component, weakness class, CVSS vector, affected version threshold, and high-level impact only. Do not infer exploit availability or root cause details beyond out-of-bounds write in GPU. The desktop-titled Google reference creates some platform ambiguity worth tracking.
Mitigation direction
- Update Chrome on Android to 148.0.7778.216 or later where available.
- Check Google's official Chrome release guidance for Android-specific remediation details.
- Prioritize managed Android fleets and high-risk user groups for update enforcement.
- Monitor vendor advisories for added platform scope, mitigations, or exploitation evidence.
Validation and detection
- Inventory Android Chrome versions across managed devices.
- Flag devices running Chrome before 148.0.7778.216.
- Confirm update deployment through MDM, endpoint telemetry, or device compliance reports.
- Review security feeds for any change in KEV or Google exploitation language.
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-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-9872 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.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/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:L/PR:N/UI:R/S:C/C:H/I:H/A:H 2.8 6 CISA-ADP Vulnerability scoring details
Base CVSS 3.1 score
9.6 CriticalVector: CVSS:3.1/AV:N/AC:L/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/505077859 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 Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.