Analyst readout for executives and security teams
Plain-English summary
CVE-2026-9920 is a Chrome on Android GPU memory-initialization flaw. If an attacker already compromises the renderer process, a crafted HTML page could leak limited cross-origin data. The public record rates CVSS low, while Chromium marks severity High.
Executive priority
Treat as a routine but prompt mobile browser update item. The business risk is mainly limited data leakage from targeted browser-chain scenarios, not broad remote takeover based on the provided evidence.
Technical view
The issue is CWE-457, uninitialized use in the GPU component. The attack path is network-delivered content requiring user interaction and high attack complexity, with no privileges required. Impact shown in the bundle is confidentiality-only and low, with no integrity or availability impact.
Likely exposure
Organizations are exposed where managed or unmanaged Android devices run Google Chrome versions prior to 148.0.7778.216. The bundle does not establish desktop impact despite including a desktop release-note reference.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Successful abuse requires a compromised renderer process first, so this is more concerning as part of a browser exploit chain than as a standalone bug.
Researcher notes
The record identifies Chrome on Android prior to 148.0.7778.216 and CWE-457 in GPU. Public details are sparse, and the Chromium issue may restrict technical detail. Do not infer exploitability, affected desktop builds, or bypass mechanics beyond the provided text.
Mitigation direction
- Update Chrome on Android to 148.0.7778.216 or later where available.
- Check Google and Chromium guidance for any additional vendor-specific mitigations.
- Prioritize managed Android fleets and high-risk users with sensitive web workflows.
- Keep renderer and site isolation hardening controls enabled where centrally managed.
Validation and detection
- Inventory Android Chrome versions across managed devices.
- Confirm no device remains below 148.0.7778.216.
- Review mobile browser update compliance in MDM or endpoint tooling.
- Track vendor release notes for clarifications on affected platforms.
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-457: 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 lookupCVE-2026-9920 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
- Low
- CVSS
- 3.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
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:U/C:L/I:N/A:N 1.6 1.4 CISA-ADP Vulnerability scoring details
Base CVSS 3.1 score
3.1 LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
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/500138014 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.
Use of Uninitialized Variable
Use of Uninitialized Variable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.