Google Chrome EUVD-2026-105494

Exploitation requires the victim using a vulnerable Chrome build (prior to 156.0.8078.47) to load attacker-controlled HTML that exercises the FileSystem component's out-of-bounds read - i.e., the user must actively browse to a malicious or compromised page (UI:R), which is the primary limiting factor. No authentication, special privileges, or non-default configuration is needed (PR:N), but the impact is inherently limited to reading memory within the renderer sandbox and does not by itself escape the sandbox or achieve code execution.

This is a genuine but moderate-priority issue, and the multiple signals are largely consistent rather than conflicting. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, score 6.5) indicates a network-reachable, low-complexity, unauthenticated flaw that nonetheless requires user interaction (loading a malicious page) and yields confidentiality-only impact with no integrity or availability effect and no scope change. Crucially, the description scopes the leak to 'memory inside the sandbox,' meaning the renderer sandbox is NOT bypassed - this is information disclosure within the sandboxed process, not a path to arbitrary code execution or host compromise, which is why Chromium rated it Medium. The EPSS score of 0.22% (12th percentile) corroborates low expected exploitation, the CVE is NOT on CISA KEV, and no public proof-of-concept is referenced, so there is no public exploit identified at time of analysis. No SSVC decision data was provided in the input. Net: a real vulnerability worth patching on the normal Chrome auto-update cadence, but not an emergency; the C:H rating slightly overstates practical impact given the disclosure is bounded to sandbox memory and typically requires chaining with an info-leak primitive to be weaponized.

An attacker hosts or compromises a web page containing crafted HTML that triggers the out-of-bounds read in Chrome's FileSystem component when a victim visits it. The flaw lets the attacker read adjacent memory within the renderer sandbox, potentially leaking sensitive data or pointer values useful for defeating ASLR in a follow-on exploit chain. No public exploit code is known, and successful attack requires the victim to actively load the malicious page.