dbcve.org
ChromeWeb browser · Google

CVE-2026-11295

HIGH · 8.8 CVSS v3.1 Published 2026-06-05
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
95/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
Inappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Low)

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

Inappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.53 allows a remote attacker to perform privilege escalation via a crafted HTML page. The vulnerability stems from improper access controls within the WebView component, which renders web content within Android applications and can access certain device capabilities.

MitigationUpdate Google Chrome on Android to version 149.0.7827.53 or later. Organizations should ensure mobile device management policies enforce browser updates and verify patch compliance 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:< 149.0.7827.53

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Confirm Google Chrome is installed on Android
    Open Settings > Apps on the Android device and look for Google Chrome in the app list, or check the Chrome app icon directly on the home screen or app drawer
    Affected if Google Chrome is not installed on the Android device - this vulnerability only affects Chrome on Android
  2. Check the installed Chrome version on Android
    Open Chrome app, tap the three-dot menu, go to Settings > About Chrome, or navigate to chrome://version in the address bar. Note the version number displayed (for example: 149.0.7827.53 or earlier)
    Affected if Version displayed is less than 149.0.7827.53 - versions prior to this are affected by the vulnerability
  3. Verify WebView component is in use
    On Android 10 and earlier, WebView is provided by the system. On Android 11+, Chrome often serves as WebView. Check Settings > Apps > Default Apps > Web browser, or for WebView specifically: Settings > Apps > Android System WebView (or WebView) - if Chrome is set as the default or Chrome's WebView is active, the vulnerability applies
    Affected if Chrome is configured as the default WebView provider or WebView browser on the device - the vulnerability resides in how Chrome handles WebView content

A user is affected if Google Chrome on Android is installed with a version number lower than 149.0.7827.53 and Chrome is being used as or alongside the WebView component.

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 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome on Android to version 149.0.7827.53 or later. Organizations should ensure mobile device management policies enforce browser updates and verify patch compliance across managed Android devices.

Recommended fix High confidence

149.0.7827.53 or later

  1. Open Google Play Store on the Android device
  2. Search for "Google Chrome" in the Play Store
  3. Tap the Update button to install the latest version of Chrome
  4. Alternatively, ensure Google Play auto-updates are enabled for Chrome by going to Play Store > Profile > Settings > Auto-update apps

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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