ChromeWeb browser · Google
CVE-2026-9889
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 · uneditedOut of bounds read and write in Dawn in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
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 confidenceOut of bounds memory read/write vulnerability in Dawn (Google's WebGPU implementation) in Google Chrome for Android before version 148.0.7778.216 allows a remote attacker to potentially escape the browser sandbox 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.
-
Confirm you are running Google Chrome for AndroidOpen Chrome, tap the three-dot menu, go to Settings, then About Chrome. Note the browser name and ensure it says Chrome (not Chrome Beta, Firefox, or another browser).Affected if The browser is not Google Chrome for Android - the vulnerability only affects this specific product.
-
Check the installed Chrome versionIn Chrome for Android, go to Settings > About Chrome. The version number is displayed next to 'Chrome'. Compare it to 148.0.7778.216.Affected if The installed version is lower than 148.0.7778.216 (for example, 148.0.7778.200 or any earlier version).
-
Verify WebGPU is enabledIn Chrome for Android, go to chrome://flags/#enable-webgpu. Check the status of the 'WebGPU' flag. Alternatively, visit a WebGPU test page to confirm the API is functional.Affected if WebGPU is enabled or active - the vulnerability exists in the Dawn WebGPU implementation, so the feature must be available for exploitation.
You are affected if you are running Google Chrome for Android with version lower than 148.0.7778.216 and WebGPU is enabled or accessible in the browser.
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. For managed Android devices, deploy MDM/EMM policies to enforce automatic Chrome updates via Google Play.
Chrome 148.0.7778.216 or later for Android
- Open the Google Play Store app on the Android device
- Search for "Google Chrome" in the search bar
- Tap on Google Chrome from the search results
- Tap the "Update" button to install version 148.0.7778.216 or later
- Alternatively, ensure auto-updates are enabled for Chrome in Play Store settings to receive the security update automatically
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9889 — 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-9889 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