CVE-2026-9912: Inappropriate implementation in GPU in Google Chrome on Android prior to 148.0.7778.216 allowed a remote at...
Inappropriate implementation in GPU in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: High)
This Chrome for Android flaw could let a malicious web page expose sensitive process memory from a vulnerable browser. It affects versions before 148.0.7778.216. The business risk is mainly information disclosure from users who browse attacker-controlled pages, with no source-bundle evidence of active exploitation.
Executive priority
Treat this as a prompt mobile browser update issue, not an emergency unless sensitive Android users are broadly unpatched. The main concern is confidentiality loss from web browsing, with no cited active exploitation evidence.
Technical view
CVE-2026-9912 is a CWE-200 information disclosure issue from an inappropriate GPU implementation in Google Chrome on Android before 148.0.7778.216. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, user interaction required, high confidentiality impact, no integrity or availability impact.
Likely exposure
Exposure is limited to Android devices running Google Chrome before 148.0.7778.216. Risk is higher for managed or BYOD mobile users who browse untrusted sites. The provided sources do not identify other affected products or platforms.
Exploitation context
The CVE describes exploitation through a crafted HTML page, requiring a user to load attacker-controlled content. The source bundle does not include exploit code, public exploitation claims, or CISA KEV listing evidence.
Researcher notes
Public detail is sparse. The Chromium issue may contain restricted information, and the bundle provides no deeper root-cause analysis beyond GPU inappropriate implementation. Do not assume exploitability beyond crafted HTML and user interaction.
Mitigation direction
Update Chrome on Android to 148.0.7778.216 or later.
Use MDM or enterprise controls to enforce Chrome updates on Android devices.
Prioritize users exposed to untrusted browsing or sensitive workflows.
Monitor Google Chrome release notes for any revised vendor guidance.
Validation and detection
Inventory Android Chrome versions across managed mobile devices.
Confirm no devices remain below 148.0.7778.216.
Review mobile browser update compliance in MDM reporting.
Check whether vulnerable devices accessed high-risk web content during the exposure window.
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 · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.