EUVD-2026-34453
GHSA-2q4w-xq2r-5pg7
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
4DescriptionCVE.org
Out of bounds read in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Out-of-bounds read in ANGLE (Almost Native Graphics Layer Engine) within Google Chrome prior to 149.0.7827.53 enables an attacker who has already compromised the renderer process to leak potentially sensitive data from process memory via a crafted HTML page. The CVSS vector (AC:H, UI:R) reflects a two-stage exploitation requirement: the attacker must first achieve renderer compromise through a separate vulnerability, then chain this ANGLE flaw as a second-stage information disclosure primitive. No public exploit code has been identified and EPSS sits at 0.03% (11th percentile), indicating low real-world exploitation probability at time of analysis.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Google's open-source graphics abstraction library used by Chrome to translate OpenGL ES API calls to platform-native graphics APIs such as Direct3D on Windows, Metal on macOS, and Vulkan. CWE-125 (Out-of-Bounds Read) is the root cause: ANGLE's shader or texture processing code reads beyond an allocated buffer boundary, exposing adjacent process memory contents to the caller. This class of bug in a GPU-accelerated graphics pipeline is notable because the graphics context can be shared across rendering boundaries, meaning process memory may contain rendered content from other origins, internal heap pointers useful for ASLR bypass, or session-related data. The affected product is Google Chrome desktop across all supported platforms for versions prior to 149.0.7827.53, as corroborated by the Chrome Stable Channel advisory and EUVD-2026-34453; no explicit CPE string was supplied in the source data.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later immediately using the browser's built-in update mechanism via Settings → Help → About Google Chrome, or through enterprise deployment tools such as Google Admin Console or third-party patch management. The vendor-released patch is confirmed at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Because exploitation requires a pre-compromised renderer process as a hard prerequisite, organizations should additionally ensure Chrome's sandbox is never disabled - specifically, avoid running Chrome with the --no-sandbox flag or equivalent policy overrides, as a functioning sandbox is the primary barrier to renderer compromise. There is no effective workaround that substitutes for patching given the network-delivered crafted-page attack vector. Enterprise environments using managed Chrome should verify via policy that deployed versions meet or exceed 149.0.7827.53.
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today