Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Permissions in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
UI spoofing in Google Chrome's Permissions subsystem prior to version 149.0.7827.53 enables remote unauthenticated attackers to misrepresent the browser's permission interface by delivering a crafted HTML page to a victim. The flaw (CWE-451) results in low-integrity impact - the attacker can deceive a user into perceiving a false permissions state, potentially manipulating consent decisions. No public exploit code exists, EPSS is 0.03% (8th percentile), CISA SSVC rates exploitation as none, and Chromium's own severity assessment is Low, placing this firmly in the routine-patching tier rather than an urgent response priority.
Technical ContextAI
CWE-451 (UI Misrepresentation of Critical Information) describes flaws where the interface presents misleading or falsified security-critical information to the user. In Chrome's Permissions subsystem, the browser displays prompts and indicators that communicate which origins have been granted access to sensitive capabilities (camera, location, notifications, etc.). An 'inappropriate implementation' in this subsystem - per Google's advisory language - means the logic governing how permission state is rendered or communicated can be subverted by attacker-controlled HTML content, causing the displayed UI to misrepresent actual permission grants or denials. The affected CPE range covers all Chrome Desktop builds prior to 149.0.7827.53 across platforms.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later - this is the vendor-released patch confirmed by the June 2026 Stable Channel Update advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome auto-updates by default on most desktop configurations; administrators managing enterprise fleets should verify deployment via Chrome Browser Cloud Management or group policy. No workarounds are documented for this vulnerability. Given that exploitation requires user interaction with a crafted HTML page, organizations with web content filtering or strict browsing controls gain some additional exposure reduction, but these are not substitutes for patching. The Chromium bug tracker reference (issues.chromium.org/issues/503614310) may provide additional technical detail once the issue is fully public.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34761
GHSA-8w93-55h9-6w38