dbcve.org
ChromeWeb browser · Google

CVE-2026-11145

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
60/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
Race in Geolocation in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker 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

A race condition in the Geolocation API in Google Chrome on Android prior to version 149.0.7827.53 allows a remote attacker to leak cross-origin data via a crafted HTML page. The vulnerability exploits timing between geolocation permission requests to bypass same-origin policy protections.

MitigationUpdate Google Chrome for Android to version 149.0.7827.53 or later. Organizations should ensure mobile devices are running current browser versions and consider MDM policies for automated 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/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. Confirm Google Chrome on Android is in use
    Open the browser and navigate to chrome://version, or check the app info in Settings > Apps > Chrome on the Android device. Verify the application name is 'Chrome' and the platform is Android.
    Affected if The browser is Google Chrome running on the Android operating system.
  2. Locate the Chrome version number
    On the chrome://version page, find the line labeled 'Chrome'. The version appears as a numeric string (for example, 148.0.7825.100). Alternatively, check the version in the Google Play Store app listing for Chrome or in Android Settings > Apps > Chrome > App info.
    Affected if The version cannot be determined or the browser is not Google Chrome.
  3. Compare installed version to the affected range
    Take the version number found in the previous step and compare it numerically to 149.0.7827.53. Note that version comparison must be done carefully (149.0.7827.53 is the first fixed version).
    Affected if The installed version is less than 149.0.7827.53 (for example, 148.0.7825.100 or 149.0.7827.50).
  4. Verify geolocation API is accessible
    While not required for the vulnerability to exist, confirm that websites can request geolocation access. Visit any site that requests location permissions and observe whether the permission prompt appears. This indicates the geolocation API is active in the browser.
    Affected if The geolocation API is functional in the browser, which means the vulnerable code path could be triggered.

A user is affected if Google Chrome on Android is installed with a version number lower than 149.0.7827.53 and the browser supports geolocation API functionality.

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 mobile devices are running current browser versions and consider MDM policies for automated updates.

Recommended fix High confidence

Chrome for Android 149.0.7827.53 or later

  1. Open Google Chrome on the Android device
  2. Navigate to the Play Store and search for Google Chrome, or open Chrome and go to chrome://settings/help
  3. Check for and install any available updates
  4. Verify the installed version by visiting chrome://version - ensure the version is 149.0.7827.53 or later
  5. Alternatively, enable auto-updates in Play Store settings to ensure future security patches are applied automatically

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-11145 — 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-11145 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