CVE-2026-9921: Uninitialized Use in WebGL in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to...
Uninitialized Use in WebGL in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin information via a crafted HTML page. (Chromium security severity: High)
This Chrome on Android flaw could let a malicious web page leak limited information across website boundaries. It requires a user to visit crafted content. The source bundle does not show known active exploitation, but browser issues still matter because exposure can be broad across mobile users.
Executive priority
Prioritize this as a routine but time-sensitive mobile browser update. It is not presented as actively exploited, but cross-origin data leakage in a widely used browser can affect many users if patching lags.
Technical view
CVE-2026-9921 is a CWE-457 uninitialized use issue in WebGL affecting Google Chrome on Android before 148.0.7778.216. A remote, unauthenticated attacker could trigger cross-origin information leakage through crafted HTML. CVSS is 4.3 with network attack vector, low complexity, required user interaction, and low confidentiality impact.
Likely exposure
Exposure is most likely where Android devices run Chrome below 148.0.7778.216, especially unmanaged or slowly updated mobile fleets. The bundle only identifies Chrome on Android; it does not establish impact for other Chromium-based browsers or platforms.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Attack requires user interaction with crafted HTML. Evidence supports information disclosure, not code execution, integrity impact, or availability impact.
Researcher notes
The release data and CVE description support a WebGL uninitialized-use information disclosure path. The provided affected entry is sparse, and one reference title mentions desktop while the CVE text says Android, so validate against Google’s final advisory before expanding scope.
Mitigation direction
Update Chrome on Android to 148.0.7778.216 or later where available.
Use MDM or endpoint controls to enforce mobile browser update compliance.
Check Google Chrome release guidance for any vendor-specific remediation details.
Treat update deferral as a mobile browser risk exception.
Validation and detection
Inventory Android Chrome versions across managed and high-risk user groups.
Confirm devices report Chrome 148.0.7778.216 or later.
Review mobile compliance dashboards for stale Chrome installations.
Track the Chromium issue and Chrome release notes for updated details.
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-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.
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.
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-457 · source CWE mapping
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.