dbcve.org
ChromeWeb browser · Google

CVE-2026-11175

HIGH · 8.8 CVSS v3.1 Published 2026-06-04
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
Incorrect security UI in Messages in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to perform UI spoofing 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

This is a UI spoofing vulnerability in Google Chrome's Messages component on Android. A remote attacker can craft a malicious HTML page that tricks users by displaying fake security UI elements, potentially leading to credential theft or other social engineering attacks. The vulnerability exists in versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome for Android to version 149.0.7827.53 or later. Organizations should ensure managed devices receive the browser update through their mobile device management (MDM) or enterprise mobility management (EMM) systems.

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 the app drawer or home screen on the Android device and look for the Google Chrome app icon, or check installed apps via Settings > Apps > See all apps
    Affected if Google Chrome is not found on the device - not affected. If found, continue to next check.
  2. Locate Chrome version information
    Open Chrome > tap the three-dot menu > tap Settings > scroll down and tap About Chrome. The version number is displayed at the top of the screen.
    Affected if Unable to locate Chrome app or version information - further investigation may be needed.
  3. Compare installed version to affected range
    Note the version number shown in About Chrome (for example, 149.0.7827.53). Compare the first three octets (149.0.7827) against the affected versions below 149.0.7827.53.
    Affected if The installed version is below 149.0.7827.53 (for example, 149.0.7827.50, 148.x.x.x, or lower) - the device is potentially affected.
  4. Verify Chrome is used with Messages functionality
    Determine if Chrome is used as the underlying browser for the Android Messages app (default behavior). This is typically the case on most Android devices using the stock Messages app.
    Affected if Chrome serves as the webview engine for Messages - the UI spoofing attack surface exists. If a third-party browser is set as default, the risk profile differs.

A device is affected if Google Chrome for Android is installed with a version number lower than 149.0.7827.53 and Chrome handles web content within the Messages app.

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 for Android to version 149.0.7827.53 or later. Organizations should ensure managed devices receive the browser update through their mobile device management (MDM) or enterprise mobility management (EMM) systems.

Recommended fix High confidence

Chrome for Android 149.0.7827.53 or later

  1. Open the Google Play Store app on your Android device
  2. Search for 'Google Chrome' or locate it in your installed apps
  3. Tap the 'Update' button to install version 149.0.7827.53 or later
  4. Once updated, close and reopen Chrome to ensure the fix is active
  5. Verify the version by navigating to chrome://version in the address bar to confirm you are on 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
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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