dbcve.org
ChromeWeb browser · Google

CVE-2025-11209

HIGH · 8.2 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 141.0.7390.54 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Omnibox in Google Chrome on Android prior to 141.0.7390.54 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) 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

Inappropriate implementation in Omnibox (URL bar) in Google Chrome on Android prior to version 141.0.7390.54 allowed a remote attacker to spoof the displayed URL via a crafted HTML page, potentially misleading users about the true origin of content.

MitigationUpdate Google Chrome for Android to version 141.0.7390.54 or later. For enterprise environments, deploy the update via MDM/EMM infrastructure to ensure fleet-wide coverage.

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:< 141.0.7390.54

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 for Android is installed
    Navigate to Settings > Apps on the Android device and look for Google Chrome in the app list, or check the Play Store for Chrome.
    Affected if Google Chrome for Android is present on the device
  2. Locate the installed Chrome version number
    Open Chrome, tap the three-dot menu, select Help > About Chrome, or go to chrome://version in the URL bar. The version is displayed at the top of the page.
    Affected if Unable to determine the version number
  3. Compare the installed version to the vulnerable range
    Review the version number displayed in the About Chrome page. Compare it to the affected range: any version prior to 141.0.7390.54 is vulnerable.
    Affected if The installed version is less than 141.0.7390.54 (for example, 141.0.7390.53, 140.x.x.x, or earlier)
  4. Verify the Omnibox (URL bar) is accessible
    Open Chrome and confirm the URL bar (Omnibox) is visible and functional at the top of the browser window.
    Affected if The Omnibox is not present or not accessible (Chrome variant or special build)
  5. Confirm the device runs Android
    Check that the device operating system is Android. This vulnerability specifically affects Chrome on Android, not iOS or other platforms.
    Affected if The device is not running Android

A user is affected if Google Chrome for Android is installed with a version lower than 141.0.7390.54 and the Omnibox URL bar is accessible on an Android device.

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

Update Google Chrome for Android to version 141.0.7390.54 or later. For enterprise environments, deploy the update via MDM/EMM infrastructure to ensure fleet-wide coverage.

Recommended fix High confidence

Chrome Android 141.0.7390.54 or later

  1. Open Google Play Store on your Android device
  2. Search for Google Chrome in the apps section
  3. Tap on Google Chrome from the search results
  4. Tap the Update button to install version 141.0.7390.54 or later
  5. Wait for the update to complete and verify the version in Chrome settings > About Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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