CVE-2025-12728: Google Chrome · Inappropriate Implementation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium : upgrade to 142.0.7444.137 when convenient.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 142.0.7444.137
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.137.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
1. Immediately update all Chrome installations on Android devices to version 142.0.7444.137 or later, as this version contains the fix for the vulnerability. 2. Implement mobile device management (MDM) policies to enforce timely browser updates and restrict installation of outdated or unapproved browser versions. 3. Educate users about the risks of interacting with suspicious or unexpected UI elements and the importance of verifying URLs before entering credentials or sensitive information. 4. Deploy phishing detection and prevention tools that can identify and block malicious URLs or pages designed to exploit UI spoofing. 5. Monitor network traffic and user reports for signs of phishing attempts or unusual browser behavior. 6. Encourage the use of multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing. 7. Coordinate with IT and security teams to conduct periodic security awareness training focused on mobile threats and browser security. 8. Consider deploying browser security extensions or enterprise policies that limit the ability of web pages to manipulate UI elements.
Description
Inappropriate implementation in Omnibox in Google Chrome on Android prior to 142.0.7444.137 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: Medium)