CVE-2025-12435: Incorrect security UI in Omnibox
Chromium: CVE-2025-12435 Incorrect security UI in Omnibox
Other sources
Incorrect 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)
— MITRE
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2025-12428
- CVE-2025-12429
- CVE-2025-12430
- CVE-2025-12431
- CVE-2025-12432
- CVE-2025-12433
- CVE-2025-12036
- CVE-2025-12434
- CVE-2025-12436
- CVE-2025-12437
- CVE-2025-12438
- CVE-2025-12439
- CVE-2025-12440
- CVE-2025-12441
- CVE-2025-12443
- CVE-2025-12444
- CVE-2025-12445
- CVE-2025-12446
- CVE-2025-12447
- CVE-2025-13226
- CVE-2025-13227
- CVE-2025-13228
- CVE-2025-13229
- CVE-2025-13230
Frequently Asked Questions
What is the severity of CVE-2025-12435?
CVE-2025-12435 is categorized as a high-severity vulnerability affecting the Chromium security UI.
How do I fix CVE-2025-12435?
To fix CVE-2025-12435, update Google Chrome to version 142.0.7444.59 or Microsoft Edge (Chromium-based) to the latest available version.
Which versions are affected by CVE-2025-12435?
CVE-2025-12435 affects Google Chrome versions prior to 142.0.7444.59 and Microsoft Edge (Chromium-based) prior to the latest release.
Is CVE-2025-12435 being actively exploited?
As of now, there are no confirmed reports of CVE-2025-12435 being actively exploited in the wild.
Who is responsible for addressing CVE-2025-12435?
Google is responsible for addressing CVE-2025-12435 as it is a vulnerability within the Chromium engine utilized by browsers like Chrome and Edge.