EUVD-2026-41171
GHSA-h7c3-2m9q-v5pc
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
AC:H reflects the hard prerequisite of a pre-compromised renderer; C:H captures memory disclosure; I:N and A:N because no write or availability impact exists.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Integer overflow in ANGLE in Google Chrome on Windows prior to 150.0.7871.46 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 abstraction layer on Windows enables a remote attacker, who has already compromised the renderer process, to read potentially sensitive data from process memory. The attack requires a user to visit a crafted HTML page, making this a second-stage component in a multi-step exploit chain rather than a standalone critical flaw. No public exploit code has been identified and CISA has not added this to the KEV catalog; Chrome 150.0.7871.46 resolves the issue.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Chrome's cross-platform OpenGL ES to native API translation layer; on Windows it converts OpenGL ES calls to DirectX. The affected component is identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* for all Chrome versions on Windows prior to 150.0.7871.46. The assigned CWE is CWE-472 (External Control of Assumed-Immutable Web Parameter), which is atypical for an integer overflow - CWE-190 (Integer Overflow or Wraparound) would be the expected classification. This mismatch suggests a possible data-quality issue in the CVE record; the true root cause is most likely an arithmetic boundary error in ANGLE's buffer or index calculations that, under an already-compromised renderer context, allows out-of-bounds memory reads disclosing process memory contents.
RemediationAI
Vendor-released patch: Chrome 150.0.7871.46. Users and administrators should update Google Chrome to version 150.0.7871.46 or later immediately via Chrome's built-in update mechanism (Settings → Help → About Google Chrome) or through enterprise deployment tools such as Google Update or WSUS-managed packages. The advisory is available at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. If immediate patching is not possible, the primary compensating control is to ensure no other renderer-compromise vulnerabilities are present in the deployed Chrome version, since this flaw is only exploitable post-renderer-compromise; restricting access to untrusted web content via enterprise policy (e.g., SafeSites filtering or URL allowlists) reduces the attack surface but does not eliminate the underlying flaw.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today