Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Incorrect security UI in Messages in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
UI spoofing in Google Chrome for Android prior to 149.0.7827.53 allows remote attackers to deceive users via crafted HTML pages that abuse the Messages component's security UI. Exploitation requires user interaction with a malicious page, and no public exploit has been identified at time of analysis. Despite a CVSS score of 8.8, EPSS exploitation probability is very low (0.03%, 11th percentile) and the issue is rated Medium by Chromium's own severity scale.
Technical ContextAI
The flaw resides in the Messages subsystem of Chrome on Android, which renders security-relevant interstitial or notification UI to the user. CWE-451 (User Interface Misrepresentation of Critical Information) describes a class of bugs where attacker-controlled content can overlay, mimic, or obscure trust-decision UI such as origin indicators, permission prompts, or warning dialogs. By delivering a crafted HTML page, the attacker can manipulate what the user sees in the Messages UI, breaking the chain of trust between the browser chrome and the underlying page origin. The affected component is specific to the Android port of Chromium and does not appear to apply to desktop builds.
RemediationAI
Vendor-released patch: Chrome for Android 149.0.7827.53. Update Chrome via the Google Play Store on all managed Android endpoints; in enterprise MDM environments, push the updated APK or enforce minimum-version policy via Android Enterprise managed configurations. Consult the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html for rollout notes. No specific workaround is documented; as a compensating control until patching completes, restrict Chrome on Android to known-good sites via DNS or proxy filtering and reinforce user awareness training on URL-bar and permission-prompt scrutiny, accepting that user-vigilance controls are unreliable against UI-spoofing bugs by definition. For downstream Chromium-based Android browsers, monitor their respective release channels for the corresponding cherry-pick.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34636
GHSA-hhhm-8p4x-8gm9