Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
AV:N and PR:N reflect network-delivered HTML vector with no authentication; AC:H captures mandatory prior renderer compromise; C:H reflects GPU memory read potential; I:N and A:N as read-only information disclosure with no write or denial impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Uninitialized Use in GPU in Google Chrome prior to 149.0.7827.197 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: High)
AnalysisAI
Uninitialized GPU memory use in Google Chrome prior to 149.0.7827.197 enables a second-stage attacker who has already compromised the renderer process to read sensitive data from GPU process memory via a crafted HTML page. Classified as CWE-457 (Use of Uninitialized Variable), the flaw creates an information disclosure path within Chrome's multi-process architecture. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation has two mandatory prerequisites: (1) the attacker must have already compromised Chrome's renderer process via a separate vulnerability - this is explicitly stated in the CVE description and is the primary limiting factor; (2) user interaction is required (UI:R in CVSS), meaning a user must load or interact with a crafted HTML page. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS scores this 5.3 (Medium) with vector AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate, unspecified Chrome renderer vulnerability to gain code execution within the sandboxed renderer process. The attacker then serves a crafted HTML page that triggers uninitialized reads in the GPU process, causing residual GPU memory - potentially containing data from other browser tabs or system GPU operations - to be returned to the attacker-controlled renderer context. … |
| Remediation | Update Google Chrome to version 149.0.7827.197 or later, as detailed in the Google stable channel update advisory at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0482630350.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-457 – Use of Uninitialized Variable
View allSame technique Information Disclosure
View allVendor StatusVendor
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-39038
GHSA-682p-m82j-vw29