EUVD-2026-40736
GHSA-8p9h-wq7m-f695
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
AV:N and UI:R reflect web-delivered delivery; AC:H captures mandatory renderer pre-compromise; PR:N since no auth on the target host is needed; C:H for process memory leakage; no integrity or availability impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in GPU in Google Chrome prior to 150.0.7871.47 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: Low)
AnalysisAI
Memory disclosure in Google Chrome's GPU component (prior to 150.0.7871.47) allows an attacker who has already achieved renderer process compromise to extract potentially sensitive information from process memory via a crafted HTML page. The attack requires both user interaction and a pre-existing renderer compromise, making this a second-stage vulnerability most useful for ASLR bypass or credential harvesting within an exploit chain. No public exploit code or active exploitation (CISA KEV) has been identified; Google rates this as Low severity internally despite the NVD CVSS 5.3 Medium score.
Technical ContextAI
The vulnerability stems from CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) in Chrome's GPU process implementation. Chrome employs a multi-process sandbox architecture where the renderer process handles HTML/CSS/JS execution and communicates with a separate GPU process for rendering acceleration. An 'inappropriate implementation' in the GPU component - likely an improper boundary check, uninitialized memory read, or unsafe cross-process buffer sharing - allows the renderer, when compromised, to issue crafted GPU commands or read-back operations that cause GPU process memory to leak back to the attacker-controlled renderer. Affected CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* with versions prior to 150.0.7871.47 on all platforms.
RemediationAI
Update Google Chrome to version 150.0.7871.47 or later, which contains the vendor-released patch as confirmed by the Chrome Stable Channel Update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome's auto-update mechanism should deliver this update automatically; administrators managing enterprise deployments should verify rollout via Chrome Browser Cloud Management. No specific workarounds are documented for this GPU component flaw; however, organizations operating in high-sensitivity environments may consider enabling Chrome's strict site isolation (--site-per-process, enabled by default in modern Chrome) to limit cross-origin memory exposure and reduce the value of any information leaked. Disabling GPU acceleration (--disable-gpu) would eliminate this attack surface but significantly degrades browser performance and is not recommended as a long-term control.
Same weakness CWE-200 – Information Exposure
View allSame 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