ChromeWeb browser · Google
CVE-2026-9912
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInappropriate 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInappropriate implementation in the GPU component of Google Chrome on Android allows a remote attacker to read process memory via a crafted HTML page. The vulnerability stems from a flaw in how the GPU handles certain operations, enabling memory disclosure without requiring user interaction beyond visiting a malicious page.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 148.0.7778.216CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Chrome for Android is installedOpen Android Settings > Apps > Chrome, or check if Chrome appears in the app drawerAffected if Chrome for Android is not installed means this CVE does not apply to the device
-
Check installed Chrome versionOpen Chrome, tap the three dots menu > Help & Feedback > About Chrome, or visit chrome://version in the address bar. Note the version number displayed.Affected if The displayed version number is less than 148.0.7778.216 (e.g., 148.0.7778.x or earlier)
-
Verify GPU processing is enabledThis is enabled by default in Chrome for Android. No user configuration required for the vulnerability to apply.Affected if Chrome for Android is running with standard GPU rendering (default state)
-
Confirm mobile device usageThis vulnerability is specific to the Android platform. Verify the Chrome browser is running on an Android device, not iOS, Desktop, or other platforms.Affected if Chrome for Android is confirmed as the browser in use
The environment is affected if Chrome for Android is installed and the version is below 148.0.7778.216.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped148.0.7778.216
Update Google Chrome on Android to version 148.0.7778.216 or later to patch the GPU implementation flaw.
Chrome 148.0.7778.216 or later for Android
- Open the Google Play Store on the Android device
- Search for "Google Chrome" or "Chrome"
- Tap on Google Chrome from the search results
- If an update is available, tap the "Update" button
- Alternatively, open Chrome and navigate to chrome://settings/help to check for and apply updates
- Verify the update completed successfully by checking Chrome's version in Settings > About Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9912 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data