dbcve.org
ChromeWeb browser · Google

CVE-2026-10010

MEDIUM · 5.0 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Inappropriate implementation in Input in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to bypass site isolation 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 confidence

This vulnerability in Google Chrome for Android's Input component allows a remote attacker who has already compromised the renderer process to bypass site isolation protections via a crafted HTML page. Site isolation is a security feature that separates different websites' processes to prevent one site from accessing another's sensitive data. The attacker exploits an inappropriate implementation flaw in how input handling interacts with these isolation boundaries.

MitigationUpdate Google Chrome for Android to version 148.0.7778.216 or later to obtain the patch. Organizations should ensure mobile device management or Chrome for Enterprise policies are enforcing the latest browser version across managed Android devices.

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

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. Check Chrome for Android version
    Open Chrome on the Android device, tap the three-dot menu, go to Settings > About Chrome to view the installed version number
    Affected if The displayed version is lower than 148.0.7778.216
  2. Confirm platform is Android
    Verify the Chrome browser is running on Android OS, not iOS, Windows, macOS, or Linux
    Affected if The browser is Chrome on Android and version is below 148.0.7778.216
  3. Confirm site isolation is enabled
    Navigate to chrome://flags/#enable-site-per-process in Chrome on Android. This flag controls site isolation. Check that it is not set to Disabled
    Affected if Site isolation has been disabled manually and the Chrome version is below 148.0.7778.216 (note: site isolation is enabled by default)
  4. Identify potential attack surface
    Review whether the device may run untrusted web content or browser extensions that could compromise the renderer process. This CVE requires an already-compromised renderer to exploit the site isolation bypass
    Affected if The device runs untrusted web content and Chrome version is below 148.0.7778.216

A user is affected if Google Chrome on Android is installed with a version lower than 148.0.7778.216 and the device runs potentially untrusted web content that could compromise the renderer process.

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 to obtain the patch. Organizations should ensure mobile device management or Chrome for Enterprise policies are enforcing the latest browser version across managed Android devices.

Recommended fix High confidence

148.0.7778.216

  1. Open Google Play Store on your Android device
  2. Search for "Google Chrome" or locate it in your installed apps
  3. If an update is available, tap "Update" to install version 148.0.7778.216 or later
  4. Alternatively, ensure Google Play Services is up to date, which often auto-updates Chrome
  5. Verify the installed version by opening Chrome, going to Settings > About Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10010 — 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-10010 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