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 implementation prior to version 149.0.7827.53 allows a remote, unauthenticated attacker to deceive users through manipulated browser permission dialogs via a crafted HTML page. Exploitation requires user interaction - a victim must visit a malicious page - and the real-world impact is limited to low-integrity outcomes such as misleading users into granting or denying permissions under false pretenses. No public exploit code exists and this vulnerability has not been added to the CISA KEV catalog at time of analysis.
Technical ContextAI
CWE-451 (User Interface Misrepresentation of Critical Information) describes flaws where the UI presents misleading or inaccurate information to the user, undermining trust decisions. In Chrome's Permissions subsystem, this implementation flaw allows a crafted HTML page to manipulate how permission prompts - such as those for geolocation, camera, microphone, or notifications - are rendered or contextualized, enabling an attacker to spoof the origin, context, or nature of a permission request. The affected codebase corresponds to Chromium's permissions UI layer, tracked in Chromium issue 498405554. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) confirms the flaw is remotely triggerable with no authentication and low complexity, but requires user interaction to reach the vulnerable code path.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later, which contains the vendor-released patch for this issue. The stable channel update is documented at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's automatic update mechanism should apply this patch without manual intervention for most users; administrators managing enterprise deployments should verify fleet-wide rollout via Google Admin Console or equivalent endpoint management tooling. No workarounds are identified for this issue given its location in the browser's core permissions UI; the only reliable mitigation is applying the patch. Given the low severity, emergency out-of-band deployment is not warranted, but inclusion in the next standard patch cycle is recommended.
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-34715
GHSA-q9xv-w349-hffr