Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-102312 Overview
CVE-2026-102312 is a user interface misrepresentation vulnerability in the Omnibox component of Google Chrome on Android. The flaw affects Chrome for Android versions prior to 154.0.8037.92. A remote attacker can craft an HTML page that spoofs the address bar, misleading users about the true origin of displayed content. Chromium rates the security severity as High. The weakness is classified as [CWE-451] (User Interface (UI) Misrepresentation of Critical Information), a category commonly abused in phishing and credential-harvesting campaigns.
Critical Impact
A crafted HTML page can spoof the Chrome for Android address bar, enabling convincing phishing pages that appear to originate from trusted domains.
Affected Products
- Google Chrome for Android versions prior to 154.0.8037.92
- Chromium-based mobile browsers sharing the affected Omnibox code path
- Android devices running vulnerable Chrome builds
Discovery Timeline
- 2026-09-29 - CVE-2026-102312 published to the National Vulnerability Database
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-102312
Vulnerability Analysis
The Omnibox is Chrome's combined address and search bar. It is the primary security indicator users rely on to verify the origin of a web page. When Omnibox rendering diverges from the actual document origin, users lose the ability to distinguish legitimate sites from attacker-controlled content.
In CVE-2026-102312, a crafted HTML page manipulates Omnibox behavior on Android to display a URL that does not match the loaded content. The mismatch enables an attacker to present a page under a spoofed domain identity. The issue is scoped to the Android build of Chrome, where address bar collapsing, tab switching, and touch interaction can create timing windows for URL misrepresentation.
Root Cause
The root cause is improper synchronization between the Omnibox display state and the underlying navigation state, consistent with [CWE-451]. During specific navigation or rendering sequences triggered by a crafted page, the address bar shows a URL that does not correspond to the origin actively serving the visible document. Full technical details are tracked in Chromium Issue #551668264.
Attack Vector
Exploitation requires a victim to visit an attacker-controlled or compromised web page in Chrome for Android. No authentication, elevated privileges, or additional software is required. Because the spoof targets the address bar itself, it is well suited to phishing scenarios that impersonate banking, enterprise SSO, or webmail login pages. See the Google Chrome Desktop Update advisory for the vendor release context.
No verified proof-of-concept code has been published. Consult the vendor advisory and Chromium issue tracker for authoritative technical detail.
Detection Methods for CVE-2026-102312
Indicators of Compromise
- User reports of Chrome for Android sessions where the address bar URL does not match visible page branding or content
- Outbound HTTPS connections from Android endpoints to newly registered domains hosting login-style HTML
- Credential submissions from mobile browsers to hosts that differ from the domain shown in browser history
Detection Strategies
- Inventory Chrome for Android versions across managed devices and flag any build below 154.0.8037.92
- Correlate mobile browser telemetry with threat intelligence on phishing infrastructure and typosquatted domains
- Inspect proxy and DNS logs for Android User-Agent strings resolving suspicious first-seen domains hosting authentication forms
Monitoring Recommendations
- Monitor MDM or UEM reporting for Chrome application version compliance on Android fleets
- Alert on repeated authentication failures followed by successful logins from mobile devices, indicating possible phished credentials
- Track user-reported phishing submissions to identify campaigns exploiting address bar spoofing
How to Mitigate CVE-2026-102312
Immediate Actions Required
- Update Google Chrome for Android to version 154.0.8037.92 or later through the Google Play Store
- Enforce a minimum Chrome version policy via MDM for all managed Android devices
- Reinforce user awareness that address bar contents alone are not sufficient proof of site identity on unpatched mobile browsers
Patch Information
Google addressed the vulnerability in Chrome 154.0.8037.92 for Android. Deployment details are available in the Chrome Releases blog and the Chromium Issue Tracker entry #551668264. Managed environments should push updates through Google Play managed configurations or enterprise mobility platforms.
Workarounds
- Restrict Chrome for Android usage for sensitive authentication workflows until devices are patched
- Require phishing-resistant authentication such as FIDO2 hardware keys or platform passkeys, which bind credentials to the true origin
- Route mobile browser traffic through an enterprise secure web gateway that blocks known phishing domains
# Example: enforce a minimum Chrome for Android version via MDM managed configuration
# (applied by your UEM vendor; syntax varies by platform)
package: com.android.chrome
minimum_version: 154.0.8037.92
auto_update: enabled
play_store_managed_config: required
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

