EUVD-2026-34570
GHSA-f6mv-9jc6-7pf8
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
Uninitialized Use in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Cross-origin data leakage in Google Chrome's ANGLE graphics library affects all versions prior to 149.0.7827.53, allowing unauthenticated remote attackers to read sensitive cross-origin browser data by enticing a user to visit a specially crafted HTML page. The root cause is uninitialized memory use (CWE-457) within ANGLE, Chrome's graphics abstraction layer, where residual memory contents from other origins can be exposed through the GPU pipeline. No public exploit identified at time of analysis, and the EPSS score of 0.03% (11th percentile) indicates low current exploitation probability; however, Chrome's broad install base makes any confirmed cross-origin data disclosure notable from a privacy and session-data standpoint.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Google's cross-platform OpenGL ES translation layer embedded in Chrome, responsible for mapping OpenGL ES calls to native graphics APIs - DirectX on Windows, Metal on macOS, and Vulkan on supported platforms. CWE-457 (Use of Uninitialized Variable) indicates that memory is allocated within ANGLE's processing pipeline but not zeroed or fully populated before being read or returned, allowing residual heap or stack contents to be observed. In a browser context, this is particularly sensitive because cross-origin data - such as pixel buffers, rendered content from other tabs or iframes, or GPU memory recycled from prior operations - may reside in uninitialized regions. Affected versions are all Chrome desktop releases prior to 149.0.7827.53, as confirmed by the EUVD entry EUVD-2026-34570 and the Google stable channel advisory.
RemediationAI
Upgrade Google Chrome to version 149.0.7827.53 or later, as confirmed by the vendor-released stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome typically updates automatically; users and administrators should verify the installed version via chrome://settings/help and force an update if needed. For enterprise environments managed via policy, push the update through Google Admin Console or equivalent MDM without delay. If immediate patching is not operationally feasible, enabling or enforcing Chrome's Site Isolation feature (--site-per-process flag or enterprise policy SitePerProcess=Enabled) reduces cross-origin data accessibility, though it is not a complete mitigation for ANGLE-level uninitialized memory. Disabling GPU hardware acceleration (chrome://settings/system, 'Use graphics acceleration when available') would remove the ANGLE code path entirely and eliminate this attack surface, but at the cost of significantly degraded rendering performance and broken WebGL functionality - suitable only as a temporary emergency control.
Same weakness CWE-457 – Use of Uninitialized Variable
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today