Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Crafted page is remotely served (AV:N, AC:L, PR:N); user must interact with spoofed dialog (UI:R); integrity is high as false permission grants alter security state; no scope change, confidentiality, or availability impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in Permissions in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
UI spoofing in Google Chrome's Permissions subsystem prior to version 150.0.7871.47 allows a remote attacker to misrepresent permission dialogs or security indicators to users via a crafted HTML page, potentially inducing unintended browser permission grants (camera, microphone, geolocation, notifications). The flaw is classified as medium severity, with no active exploitation confirmed - CISA KEV listing is absent, no public POC is known, and EPSS places exploitation probability at 0.17% (7th percentile). Vendor-released patch is available in Chrome 150.0.7871.47.
Technical ContextAI
The root cause is classified as CWE-451 (User Interface Misrepresentation of Critical Information), meaning the Chrome Permissions subsystem fails to correctly enforce boundaries that prevent attacker-controlled page content from altering, overlaying, or spoofing security-critical UI elements - specifically the permission prompt mechanism. Chrome's permission system is responsible for mediating origin-level capability grants; when its implementation behaves inappropriately in response to crafted HTML, the displayed prompt no longer faithfully represents the true security context, breaking the trust model users rely upon to make informed grant decisions. The affected product is identified via CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all Chrome desktop builds prior to 150.0.7871.47.
RemediationAI
The primary fix is to upgrade Google Chrome to version 150.0.7871.47 or later; this is the vendor-released patched version confirmed by the stable channel update advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome's auto-update mechanism should apply this transparently for most users; administrators should verify the installed version is at or above 150.0.7871.47 via chrome://settings/help. SUSE users running repackaged Chromium should apply the corresponding distribution package update via zypper or the SUSE update channel once published. As a compensating control prior to patching, users and enterprise policy managers can configure Chrome to block all permission requests from unknown or untrusted origins using chrome://settings/content - the trade-off is that this will also block legitimate permission prompts from sites that have not been pre-approved.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40684
GHSA-33j7-4593-xh6r