CVE-2025-12447: Incorrect security UI in Google Chrome
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)
AI Analysis
Technical Summary
CVE-2025-12447 is a security vulnerability identified in the Omnibox component of Google Chrome on Android platforms prior to version 142.0.7444.59. The flaw arises from an incorrect security user interface implementation, which can be manipulated by a remote attacker through a crafted HTML page. By persuading a user to perform specific UI gestures, the attacker can trigger UI spoofing, effectively misleading the user about the authenticity or security state of the browser interface. This could facilitate phishing attacks or trick users into divulging sensitive information or performing unintended actions. The vulnerability does not require any prior authentication but does require user interaction, specifically the execution of certain UI gestures. The CVSS v3.1 base score is 4.2, reflecting a medium severity level, with attack vector network (remote), high attack complexity, no privileges required, user interaction required, unchanged scope, low confidentiality impact, no integrity impact, and low availability impact. No known exploits have been reported in the wild as of the publication date, and no patch links were provided, but the issue is resolved in Chrome version 142.0.7444.59. The underlying weakness is categorized under CWE-306, indicating an incorrect security UI that can mislead users about security status.
Potential Impact
For European organizations, the primary risk posed by this vulnerability lies in the potential for successful phishing or social engineering attacks that exploit UI spoofing to deceive users. This can lead to unauthorized disclosure of sensitive information such as credentials or personal data, especially in environments where Chrome on Android is widely used for accessing corporate resources. Although the confidentiality impact is rated low, the risk of user deception can facilitate further attacks, including account compromise or malware installation. The availability and integrity impacts are minimal. The requirement for user interaction and high attack complexity reduces the likelihood of widespread exploitation, but targeted attacks against high-value individuals or sectors remain a concern. Organizations with mobile workforces relying on Chrome for Android should be particularly vigilant. Additionally, sectors with stringent data protection requirements under GDPR may face compliance risks if user data is compromised through such attacks.
Mitigation Recommendations
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.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Sweden, Belgium, Poland, Ireland
CVE-2025-12447: Incorrect security UI in Google Chrome
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)
AI-Powered Analysis
Technical Analysis
CVE-2025-12447 is a security vulnerability identified in the Omnibox component of Google Chrome on Android platforms prior to version 142.0.7444.59. The flaw arises from an incorrect security user interface implementation, which can be manipulated by a remote attacker through a crafted HTML page. By persuading a user to perform specific UI gestures, the attacker can trigger UI spoofing, effectively misleading the user about the authenticity or security state of the browser interface. This could facilitate phishing attacks or trick users into divulging sensitive information or performing unintended actions. The vulnerability does not require any prior authentication but does require user interaction, specifically the execution of certain UI gestures. The CVSS v3.1 base score is 4.2, reflecting a medium severity level, with attack vector network (remote), high attack complexity, no privileges required, user interaction required, unchanged scope, low confidentiality impact, no integrity impact, and low availability impact. No known exploits have been reported in the wild as of the publication date, and no patch links were provided, but the issue is resolved in Chrome version 142.0.7444.59. The underlying weakness is categorized under CWE-306, indicating an incorrect security UI that can mislead users about security status.
Potential Impact
For European organizations, the primary risk posed by this vulnerability lies in the potential for successful phishing or social engineering attacks that exploit UI spoofing to deceive users. This can lead to unauthorized disclosure of sensitive information such as credentials or personal data, especially in environments where Chrome on Android is widely used for accessing corporate resources. Although the confidentiality impact is rated low, the risk of user deception can facilitate further attacks, including account compromise or malware installation. The availability and integrity impacts are minimal. The requirement for user interaction and high attack complexity reduces the likelihood of widespread exploitation, but targeted attacks against high-value individuals or sectors remain a concern. Organizations with mobile workforces relying on Chrome for Android should be particularly vigilant. Additionally, sectors with stringent data protection requirements under GDPR may face compliance risks if user data is compromised through such attacks.
Mitigation Recommendations
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.
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Chrome
- Date Reserved
- 2025-10-28T20:16:50.935Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 6912465d941466772c506b45
Added to database: 11/10/2025, 8:09:01 PM
Last enriched: 11/17/2025, 9:05:52 PM
Last updated: 11/22/2025, 6:38:27 AM
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-11186: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in humanityco Cookie Notice & Compliance for GDPR / CCPA
MediumCVE-2025-2609: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in MagnusSolution MagnusBilling
HighCVE-2024-9643: CWE-489 Active Debug Code in Four-Faith F3x36
CriticalCVE-2025-65947: CWE-400: Uncontrolled Resource Consumption in jzeuzs thread-amount
HighCVE-2025-65946: CWE-77: Improper Neutralization of Special Elements used in a Command ('Command Injection') in RooCodeInc Roo-Code
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.