dbcve.org
ChromeWeb browser · Google

CVE-2026-11007

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/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
Insufficient validation of untrusted input in WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to leak cross-origin data 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 · moderate confidence

Insufficient validation of untrusted input in WebView in Google Chrome on Android prior to version 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to leak cross-origin data via a crafted HTML page.

MitigationUpdate Google Chrome on Android to version 149.0.7827.53 or later. For enterprise environments, ensure mobile device management policies enforce Chrome updates.

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
None
Availability
None

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

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 Android Chrome or WebView is in use
    Determine whether the target application uses Google Chrome on Android or the Android System WebView component. Check the app in question or test the device's WebView by opening chrome://version in Chrome or checking Settings > Apps > Android System WebView.
    Affected if The device runs any app that relies on Android System WebView or uses Google Chrome on Android.
  2. Check Google Chrome version on Android
    Open Chrome, tap the three-dot menu, go to Settings, scroll to Chrome and tap it, or navigate to chrome://version. Note the version number displayed.
    Affected if The installed Chrome version is lower than 149.0.7827.53.
  3. Check Android System WebView version
    Go to Settings > Apps > Android System WebView. View the app info to see the version number.
    Affected if The WebView version is lower than 149.0.7827.53 and is used as the system's WebView provider.
  4. Verify the vulnerability context
    Confirm that the Chrome or WebView instance could be exposed to untrusted HTML content from remote sources. This is a post-compromise issue requiring the renderer process to already be compromised.
    Affected if The device has been compromised at the renderer level and runs a vulnerable WebView version.

The environment is affected if the Android device runs Google Chrome or Android System WebView with a version number lower than 149.0.7827.53.

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. For enterprise environments, ensure mobile device management policies enforce Chrome updates.

Recommended fix High confidence

Chrome 149.0.7827.53 or later for Android

  1. Open Google Chrome on Android
  2. Navigate to the Play Store and search for Google Chrome
  3. Tap Update to install version 149.0.7827.53 or later
  4. Alternatively, go to Chrome Settings > Help & Feedback > About Chrome to trigger a version check and update
  5. Verify the update was applied by checking Settings > Help & Feedback > About Chrome shows version 149.0.7827.53 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
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,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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