dbcve.org
ChromeWeb browser · Google

CVE-2026-11167

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 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
Inappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

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 confidence

A sandbox escape vulnerability in Google Chrome's WebView on Android allows a remote attacker who has already compromised the renderer process to escape the sandbox via a specially crafted HTML page. This affects any Android application that uses the WebView component.

MitigationUpdate Google Chrome on Android to version 149.0.7827.53 or later. Organizations with WebView-dependent applications should verify that Chrome is updated across managed devices and test WebView functionality after the update.

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
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 Chrome for Android installation
    On the Android device, navigate to Settings > Apps > Chrome, or open Chrome and go to chrome://version to view the version information.
    Affected if Chrome for Android is installed on the device.
  2. Determine the installed Chrome version
    In Chrome, tap the three-dot menu > Help and Feedback > About Chrome, or visit chrome://version. Note the version number displayed (e.g., 149.0.x.x).
    Affected if Chrome is installed and a version number is displayed.
  3. Compare version against vulnerability range
    Compare the installed version number to the affected range: any version below 149.0.7827.53 is vulnerable. The format is major.minor.build.patch (e.g., 148.0.6000.1 is below 149.0.7827.53).
    Affected if The installed Chrome version is less than 149.0.7827.53 (e.g., 148.x.x.x, 147.x.x.x, etc.).
  4. Confirm WebView usage context
    Determine if the organization uses Chrome as the system WebView or if apps rely on Android System WebView (chrome://components). Check if Chrome is set as the default browser or used by enterprise apps.
    Affected if Chrome for Android is actively used as the WebView component for rendering web content in applications.

The environment is affected if Chrome for Android is installed and the installed version is below 149.0.7827.53, with the sandbox escape only applicable when an attacker has already compromised 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 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 with WebView-dependent applications should verify that Chrome is updated across managed devices and test WebView functionality after the update.

Recommended fix High confidence

Chrome 149.0.7827.53 or later for Android

  1. Open Google Play Store on the Android device
  2. Search for Google Chrome
  3. If an update is available, tap Update to install version 149.0.7827.53 or later
  4. Alternatively, ensure Android System WebView is updated via Google Play Store (Chrome updates include WebView updates on most modern Android versions)
  5. Restart the browser after updating

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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