Google Chrome EUVD-2026-105667

Exploitation requires the victim to use a Chrome desktop build prior to 156.0.8078.47 and to actively load attacker-controlled HTML content (UI:R), so it cannot be triggered silently or server-side - the victim must visit or be redirected to the crafted page. No authentication is required (PR:N) and no special non-default Chrome configuration is indicated by the description; the flaw resides in the Ozone component (Chrome's platform windowing/graphics abstraction), which is part of the standard desktop build. The primary limiting factors are the required user interaction (browsing to the malicious page) and the patched version boundary; impact is limited to disclosure of sensitive information with no integrity or availability effect.

This is a medium-severity (CVSS 6.5) improper access control flaw (CWE-284) in Chrome's Ozone component, confirmed and patched by Google/Chromium. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) indicates a network-reachable, low-complexity, unauthenticated attack that requires user interaction and yields a pure confidentiality impact with no integrity or availability effect - consistent with the description of leaking sensitive information via a crafted HTML page. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active exploitation or weaponization; the severity is driven by Chrome's enormous install base rather than by an urgent exploitation signal. Chromium's own rating of 'Medium' aligns with the C-only impact and the user-interaction requirement, suggesting this is a patch-on-normal-cycle browser bug rather than an emergency. One data inconsistency to verify: the input Tags include 'Authentication Bypass,' but the description and CWE-284 describe an access-control information leak, not an authentication bypass - treat the tag as unreliable. Overall, prioritize via standard browser patch management; this is not currently a high-urgency, actively-exploited threat based on available signals.

An attacker hosts or injects a crafted HTML page and lures a victim running a vulnerable Chrome build (prior to 156.0.8078.47) into visiting it. When the page renders, it abuses the improper access control in the Ozone layer to read sensitive information the origin should not have access to. No public exploit code was identified at the time of analysis, and successful exploitation depends on the victim actually loading the malicious page.