EUVD-2026-34560
GHSA-qg2w-2fj8-qpw3
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in GPU in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Cross-origin data leakage in Google Chrome's GPU component (prior to 149.0.7827.53) allows a remote attacker who has already compromised the renderer process to exfiltrate sensitive cross-origin information by delivering a specially crafted HTML page. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) assigns a score of 6.5 Medium, reflecting high confidentiality impact tempered by required user interaction and the critical prerequisite of a pre-compromised renderer. No public exploit has been identified at time of analysis, and EPSS registers at 0.05% (15th percentile), consistent with a multi-stage exploitation barrier.
Technical ContextAI
The flaw resides in Chrome's GPU process, which operates as a distinct privilege layer within Chrome's multi-process sandbox architecture. The root cause is CWE-20 (Improper Input Validation): the GPU component fails to adequately validate untrusted input originating from the renderer process, allowing a compromised renderer to supply maliciously crafted data that causes the GPU process to disclose cross-origin memory or pixel data. Chrome's site isolation and renderer sandbox are intended to prevent exactly this kind of inter-process data leakage, making this a sandbox-escape-adjacent flaw in the renderer-to-GPU IPC channel. The affected product is Google Chrome for desktop on all platforms prior to version 149.0.7827.53, as confirmed by ENISA EUVD record EUVD-2026-34560. No CPE string was provided in source data; the affected range is derivable as cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* for versions below 149.0.7827.53.
RemediationAI
Vendor-released patch: Google Chrome 149.0.7827.53. Users and administrators should update to this version or later immediately via Chrome's built-in auto-update mechanism or by downloading directly from the vendor. The stable channel release advisory is at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. For enterprise environments unable to immediately deploy the update, compensating controls include enforcing Chrome's Enhanced Safe Browsing policy to block access to untrusted or unrecognized web content, using enterprise web filtering to restrict browsing to known-good domains, and monitoring for anomalous cross-origin network activity that could indicate data exfiltration. Note that these controls reduce exposure but do not eliminate the vulnerability - they specifically raise the barrier to the initial renderer compromise step that this flaw depends on. Chromium-based browser vendors (Edge, Brave, Opera, etc.) should be monitored for their own patch releases incorporating the upstream fix.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today