CVE-2025-12447: Google Chrome · Incorrect Security UI
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium : upgrade to 142.0.7444.59 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 142.0.7444.59
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Google Chrome to 142.0.7444.59.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
European organizations should ensure that all Android devices running Google Chrome are updated promptly to version 142.0.7444.59 or later, which contains the fix for this vulnerability. Mobile device management (MDM) solutions should enforce update policies to minimize the window of exposure. User awareness training should emphasize caution when interacting with unfamiliar web pages and performing unusual UI gestures, highlighting the risk of UI spoofing attacks. Security teams should monitor for phishing campaigns that might leverage this vulnerability and employ web filtering solutions to block access to known malicious sites. Additionally, implementing multi-factor authentication (MFA) can reduce the impact of credential theft resulting from successful phishing. Organizations should also review their incident response plans to include scenarios involving UI spoofing and social engineering attacks on mobile platforms.
Description
Incorrect security UI in Omnibox in Google Chrome on Android prior to 142.0.7444.59 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)