CVE-2026-3925: Incorrect security UI in LookalikeChecks
Chromium: CVE-2026-3925 Incorrect security UI in LookalikeChecks
Other sources
Incorrect security UI in LookalikeChecks in Google Chrome on Android prior to 146.0.7680.71 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-2026-3913
- CVE-2026-3914
- CVE-2026-3915
- CVE-2026-3916
- CVE-2026-3917
- CVE-2026-3918
- CVE-2026-3919
- CVE-2026-3920
- CVE-2026-3921
- CVE-2026-3922
- CVE-2026-3923
- CVE-2026-3924
- CVE-2026-3926
- CVE-2026-3927
- CVE-2026-3928
- CVE-2026-3929
- CVE-2026-3930
- CVE-2026-3931
- CVE-2026-3932
- CVE-2026-3934
- CVE-2026-3935
- CVE-2026-3936
- CVE-2026-3937
- CVE-2026-3938
- CVE-2026-3939
- CVE-2026-3940
- CVE-2026-3941
- CVE-2026-3942
Frequently Asked Questions
What is the severity of CVE-2026-3925?
CVE-2026-3925 is classified as a moderate severity vulnerability due to the potential for UI spoofing.
How do I fix CVE-2026-3925?
To mitigate CVE-2026-3925, update Google Chrome for Android to version 146.0.7680.71 or later.
What type of attacks does CVE-2026-3925 enable?
CVE-2026-3925 allows attackers to perform UI spoofing via crafted HTML pages.
Which versions of Google Chrome are affected by CVE-2026-3925?
CVE-2026-3925 affects Google Chrome on Android versions prior to 146.0.7680.71.
Can CVE-2026-3925 affect other browsers besides Chrome?
While CVE-2026-3925 primarily affects Google Chrome, it may also affect Chromium-based browsers like Microsoft Edge.