Description

Use of uninitialized resource in GPU in Google Chrome prior to 151.0.7922.169 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "3.1",
  "pubDate": "2026-08-18T21:18:28.283Z",
  "pubdate": "2026-08-18T21:18:28.283Z",
  "executiveSummary": "A high-severity vulnerability involving the use of an uninitialized resource exists within the GPU component of Google Chrome prior to version 151.0.7922.169.\nThe vulnerability allows a remote attacker who has already successfully compromised the renderer process to read memory outside the security sandbox boundaries via a specially crafted HTML page.\nThis memory disclosure flaw poses significant risk implications regarding information leakage, potentially exposing sensitive heap data or internal structures that could facilitate further exploitation chains.\nThe attacker is required to leverage a preliminary compromise of the renderer process and entice a user to visit a malicious HTML page to trigger the memory read condition.",
  "technicalDetails": "The root cause of the vulnerability stems from the use of an uninitialized resource within the GPU process handling routines in Google Chrome.\nThe vulnerable component is the GPU subsystem responsible for processing graphics-related commands and state management.\nAffected software versions include Google Chrome prior to 151.0.7922.169.\nThe attack vector involves network exposure through a crafted HTML page rendered or processed within the browser context.\nPrerequisites for a successful attack require the adversary to first achieve code execution or compromise within the isolated renderer process, typically via a separate vulnerability such as a remote code execution or logic flaw.\nOnce the renderer process is compromised, the attacker interacts with the GPU process via inter-process communication (IPC) or shared resources.\nDue to the failure to properly initialize resources within the GPU component, interacting with the uninitialized memory space allows the compromised renderer to bypass sandbox restrictions and read arbitrary out-of-bounds memory.\nThe payload behavior involves querying or accessing the uninitialized memory structures to extract sensitive data residing in the address space of the GPU process.\nThe post-exploitation impact includes unauthorized information disclosure, leaking critical memory pointers, or bypassing address space layout randomization (ASLR) primitives to support subsequent sandbox escape or privilege escalation exploits."
}