ChromeWeb browser · Google
CVE-2025-12435
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 · uneditedIncorrect security UI in Omnibox in Google Chrome on Android prior to 142.0.7444.59 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 confidenceUI spoofing vulnerability in Chrome for Android's Omnibox (address bar) allows remote attackers to manipulate security indicators displayed to users via crafted HTML pages, potentially tricking users into believing they're on a different site than they actually are.
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
< 142.0.7444.59CVSS 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
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome for Android is installedOpen the device settings, go to Apps or Applications, and look for Google Chrome in the app listAffected if Google Chrome for Android is not present on the device
-
Find the installed Chrome versionOpen Chrome, tap the three-dot menu, go to Settings, then tap About Chrome. The version number is displayed on this pageAffected if Unable to locate version information in the app
-
Compare version against the affected rangeCheck if the installed version is less than 142.0.7444.59. Note that version numbers follow format Major.Minor.Build.PatchAffected if Installed version is a number lower than 142.0.7444.59 (for example, 141.x.x.x or 140.x.x.x)
-
Verify the Omnibox is accessibleOpen Chrome and confirm the address bar (Omnibox) is visible and functional at the top of the browser windowAffected if The Omnibox is not present or disabled (this is unlikely in standard Chrome for Android)
A device is affected if Google Chrome for Android is installed with a version number lower than 142.0.7444.59, as the UI spoofing vulnerability in the Omnibox exists in those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped142.0.7444.59
Update Google Chrome for Android to version 142.0.7444.59 or later. Organizations should ensure mobile devices are running the patched browser version.
Chrome 142.0.7444.59 or later for Android
- Open the Google Play Store app on your Android device
- Search for 'Google Chrome' or locate it in your installed apps
- If an update is available, tap the 'Update' button
- Wait for the update to download and install automatically
- Launch Google Chrome after the update completes, or restart your browser if already open
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12435 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12435 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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