dbcve.org
ChromeWeb browser · Google

CVE-2026-9875

CRITICAL · 9.6 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Out of bounds read in WebGL 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 · moderate confidence

Out-of-bounds read vulnerability in WebGL component of Google Chrome on Android prior to version 148.0.7778.216 allows a remote attacker to potentially escape browser sandbox protections via a maliciously crafted HTML page.

MitigationUpdate Google Chrome for Android to version 148.0.7778.216 or later; enterprise environments should deploy updates via MDM and verify patch compliance across device fleet.

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
Affected:< 148.0.7778.216

CVSS 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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the target browser is Google Chrome on Android
    Check the browser name and platform. This vulnerability only affects Google Chrome running on Android devices, not desktop Chrome, Chrome iOS, or other browsers like Firefox on Android.
    Affected if The target is not Google Chrome on Android, the detection does not apply.
  2. Locate the installed Chrome version on Android
    Open Chrome, tap the three dots menu, go to Settings > About Chrome, or open chrome://version in the address bar. Note the version number displayed (e.g., 148.0.7778.200).
    Affected if Cannot determine the version number from the device.
  3. Compare the installed version to the affected range
    Compare the version number found in step 2 to 148.0.7778.216. If the installed version is lower (e.g., 147.x.x.x or 148.0.7778.200), the browser is within the affected range.
    Affected if The installed version is less than 148.0.7778.216 (e.g., 147.x.x.x, 148.0.7778.200, or any earlier version).
  4. Verify WebGL is enabled (attack surface check)
    In Chrome on Android, go to Settings > Advanced > Privacy and security > Security, or visit chrome://flags and search for 'WebGL'. Check if WebGL is currently enabled or disabled.
    Affected if WebGL is enabled; this is the component with the vulnerability. Even if disabled, the version check in step 3 still determines if the browser is vulnerable should WebGL be turned on.

The environment is affected if the device runs Google Chrome on Android with version lower than 148.0.7778.216, regardless of WebGL enablement status.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 148.0.7778.216 or later
Fixed in 148.0.7778.216
Interim mitigation

Update Google Chrome for Android to version 148.0.7778.216 or later; enterprise environments should deploy updates via MDM and verify patch compliance across device fleet.

Recommended fix High confidence

148.0.7778.216 (Chrome for Android)

  1. Open Google Play Store on your Android device
  2. Search for "Google Chrome" or locate it in your app list
  3. Tap "Update" to install the latest version of Chrome for Android
  4. Ensure the updated version is 148.0.7778.216 or later
  5. Restart the browser after the update completes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9875 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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