ChromeWeb browser · Google
CVE-2026-9898
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 · uneditedInsufficient validation of untrusted input in GPU in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 · moderate confidenceInsufficient validation of untrusted input in the GPU component of Google Chrome on Android allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox and execute code outside the sandboxed environment via a crafted HTML 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
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.
-
Verify the browser is Google Chrome on AndroidOpen Chrome, tap the three-dot menu, then tap Settings. Confirm the app name at the top displays 'Chrome' and the device is running Android.Affected if The browser is Google Chrome on Android (this vulnerability does not affect desktop Chrome or other browsers)
-
Find the installed Chrome version on AndroidIn Chrome settings, tap 'About Chrome'. The version number is displayed at the top (for example, it may show something like 148.0.7778.215 or an earlier version).Affected if This step is required to determine if the version falls within the affected range
-
Compare installed version against the affected rangeCheck if the version shown in About Chrome is less than 148.0.7778.216. Note that version numbers are compared numerically - any version below 148.0.7778.216 (including 147.x.x.x or earlier) is in the affected range.Affected if The installed version is less than 148.0.7778.216 (for example, 147.5.1234.56 or 146.0.9999.99)
You are affected if you are running Google Chrome on Android with a version number lower than 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 for Android to version 148.0.7778.216 or later to patch the GPU input validation vulnerability. Organizations using Android WebView in their applications should test for compatibility impacts after applying the update.
Chrome 148.0.7778.216 or later for Android
- Open the Google Play Store on your Android device
- Search for 'Google Chrome' or 'Chrome'
- Tap on the Chrome app listing
- If an update is available, tap the 'Update' button
- Ensure the updated version is 148.0.7778.216 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9898 — 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-9898 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