EUVD-2026-34512
GHSA-q545-rccv-33g7
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Race in GPU in Google Chrome on Android 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 for Android (prior to 149.0.7827.53) is enabled by a race condition in the GPU component, exploitable only after the attacker has already achieved renderer process compromise. Using a crafted HTML page, the attacker can then trigger the GPU race to read cross-origin data, constituting a second-stage information disclosure step in a broader attack chain. No public exploit code or CISA KEV listing exists at time of analysis; EPSS sits at 0.03% (11th percentile), consistent with limited real-world exploitation activity.
Technical ContextAI
The vulnerability resides in the GPU process of Chromium on Android, classified under CWE-457 (Use of Uninitialized Variable). In Chromium's multi-process architecture, the GPU process handles accelerated compositing and rendering tasks on behalf of renderer processes. A race condition - a time-of-check/time-of-use (TOCTOU) class issue - between competing GPU operations can result in uninitialized or cross-origin GPU memory being read before proper isolation boundaries are enforced. CWE-457 in this context implies that the race window allows access to a memory region holding data from a different origin before it has been cleared or re-initialized, violating the Same-Origin Policy at the GPU layer. The affected product range per ENISA EUVD (EUVD-2026-34512) is Chrome versions below 149.0.7827.53 on Android. No CPE string was provided in the intelligence data.
RemediationAI
The primary fix is updating Google Chrome for Android to version 149.0.7827.53 or later, per the vendor-released patch confirmed through the Google Stable Channel Update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Android users should ensure automatic updates are enabled in the Google Play Store to receive this patch promptly. As a compensating control prior to patching, organizations with high-risk user populations can enforce Chrome version policies via mobile device management (MDM) to block versions below 149.0.7827.53. Given that exploitation requires a pre-compromised renderer process, hardening the renderer attack surface - such as deploying Chrome's Site Isolation feature if not already active and restricting access to high-risk web content via proxy filtering - reduces the likelihood that an attacker can reach the GPU race condition stage. No meaningful workaround eliminates the GPU race itself without patching.
Same weakness CWE-457 – Use of Uninitialized Variable
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today