EUVD-2026-34448
GHSA-whpv-cjp5-g2gh
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Integer overflow in ANGLE in Google Chrome on Windows 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
Integer overflow in Chrome's ANGLE graphics layer on Windows enables process memory disclosure for attackers who have already compromised the renderer process. Affected versions are all Google Chrome releases prior to 149.0.7827.53 on Windows. An attacker who has first achieved renderer compromise can trigger the ANGLE integer overflow via a crafted HTML page to read potentially sensitive data from process memory - functioning as a second-stage information leak within a chained exploit. No public exploit identified at time of analysis, and EPSS at 0.03% (11th percentile) reflects low observed exploitation probability.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Google's cross-platform OpenGL ES to native API translation layer embedded in Chrome, used to handle GPU-accelerated rendering. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* on Windows, fixed at version 149.0.7827.53. CWE-190 (Integer Overflow or Wraparound) is the root cause: arithmetic on integer values controlling memory buffer sizing or indexing in ANGLE overflows its type boundary, producing an incorrectly small or negative value that causes subsequent memory reads to access regions outside the intended buffer. On Windows, this manifests as an out-of-bounds read within the GPU or renderer process address space, potentially surfacing addresses, heap contents, or other sensitive values to a controlled JavaScript context. This class of bug in graphics drivers and translation layers is well-documented and has historically yielded sandbox-escape primitives when chained with a write primitive.
RemediationAI
Upgrade Google Chrome on Windows to version 149.0.7827.53 or later, which is the vendor-released patch per the stable channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome typically auto-updates; administrators managing enterprise deployments should verify version enforcement via policy and push the update to all Windows endpoints. As a compensating control pending update, disabling GPU hardware acceleration in Chrome (Settings → System → 'Use graphics acceleration when available') removes the ANGLE rendering path at the cost of degraded rendering performance and increased CPU usage. Restricting access to untrusted web content via enterprise browsing policies (e.g., Site Isolation, allowlisting) reduces exposure but does not eliminate the vulnerability. Given that exploitation requires a pre-compromised renderer, any defense that prevents initial renderer compromise (e.g., keeping Chrome fully patched, enabling Chrome's Enhanced Safe Browsing) also breaks the prerequisite attack chain.
Same weakness CWE-190 – Integer Overflow or Wraparound
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today