CVE-2026-9919: Out of bounds read in WebGL in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker t...
Out of bounds read in WebGL in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
This is a browser data-exposure flaw in Chrome on Android. A malicious web page could cause Chrome's WebGL handling to read outside expected memory and leak limited cross-origin data. The CVSS score is medium, but browser exposure is broad, so organizations should prioritize mobile browser updates.
Executive priority
Treat as a timely mobile browser patching issue, not a confirmed emergency. The business risk is data exposure from malicious web content, with no active exploitation cited in the provided sources.
Technical view
CVE-2026-9919 is a CWE-125 out-of-bounds read in WebGL affecting Google Chrome on Android before 148.0.7778.216. The published vector is network-based, low complexity, no privileges required, with required user interaction. Impact is limited to confidentiality, specifically possible cross-origin data leakage via crafted HTML.
Likely exposure
Exposure is likely on Android devices running Chrome versions earlier than 148.0.7778.216. Risk is highest where mobile browser patching is unmanaged or delayed. The bundle does not identify other Chromium-based browsers as affected.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires a user to load a crafted HTML page. Public issue details may be limited, and the supplied release reference appears desktop-focused, so Android-specific remediation evidence is incomplete.
Researcher notes
The CVE description provides the core condition and impact, but the source bundle lacks detailed root-cause notes, proof-of-concept status, or Android release notes. Do not assume broader Chromium impact without vendor confirmation.
Mitigation direction
Update Chrome on Android to 148.0.7778.216 or later where available.
Check Google Chrome release guidance for Android-specific update status.
Prioritize managed Android fleets with delayed browser updates.
Use mobile device management to enforce current Chrome versions.
Monitor vendor advisories for additional Chromium-based browser impact.
Validation and detection
Inventory Android devices and installed Chrome versions.
Flag Chrome versions earlier than 148.0.7778.216 as potentially exposed.
Confirm update deployment through MDM, EMM, or endpoint inventory.
Review browser update compliance for unmanaged BYOD access.
Track the Chromium issue and CVE record for changed scope.
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-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.
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-125 · source CWE mapping
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.