Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-95324 Overview
CVE-2026-95324 is an uninitialized resource vulnerability [CWE-908] in the GPU component of Google Chrome. The flaw affects Chrome versions prior to 154.0.8037.57. A remote attacker who has already compromised the renderer process can read memory outside the sandbox by serving a crafted HTML page. Chromium classifies the underlying security severity as High, though the assigned CVSS score reflects the requirement for a prior renderer compromise and user interaction. The bug enables information disclosure rather than direct code execution, and successful exploitation typically requires chaining with a separate renderer exploit.
Critical Impact
An attacker with a compromised renderer process can read memory outside the Chrome sandbox, potentially exposing sensitive data from the GPU process address space.
Affected Products
- Google Chrome Desktop versions prior to 154.0.8037.57
- Chromium-based browsers integrating vulnerable GPU code paths
- All supported desktop platforms (Windows, macOS, Linux) running affected Chrome builds
Discovery Timeline
- 2026-09-29 - CVE-2026-95324 published to the National Vulnerability Database
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-95324
Vulnerability Analysis
The vulnerability resides in Chrome's GPU process, which handles hardware-accelerated rendering, WebGL, and related graphics APIs. An uninitialized resource is allocated and subsequently accessed before its contents are set to a known state. When the renderer process, already under attacker control, requests GPU operations through a crafted HTML page, the response reflects stale memory content from the GPU process. This allows the attacker to exfiltrate data that resides outside the renderer sandbox boundary.
Because the GPU process runs at a higher privilege level than sandboxed renderers, information leaked from its address space may include cross-origin data, GPU driver state, or fragments useful for bypassing address space layout randomization (ASLR).
Root Cause
The root cause is classified as CWE-908: Use of Uninitialized Resource. Chrome's GPU code path allocates a buffer or object without zero-initializing or fully populating it before returning data to the caller. The gap between allocation and initialization exposes residual bytes from previously freed allocations.
Attack Vector
Exploitation requires two conditions. First, the attacker must already control the renderer process through a separate vulnerability. Second, the victim must load a crafted HTML page that triggers the vulnerable GPU code path. The attack traverses the renderer-to-GPU IPC boundary and returns uninitialized memory content to the compromised renderer.
No verified proof-of-concept code is publicly available. See the Chromium Issue Report #537857253 for technical details as they become public.
Detection Methods for CVE-2026-95324
Indicators of Compromise
- Chrome browser processes running versions earlier than 154.0.8037.57 on managed endpoints
- Unexpected renderer process crashes preceding or following GPU process anomalies
- Outbound connections from browser sessions to attacker-controlled infrastructure hosting crafted HTML payloads
Detection Strategies
- Inventory Chrome installations across the fleet and flag versions below 154.0.8037.57 for remediation
- Monitor for prerequisite renderer-compromise exploits, since this vulnerability requires a chained attack
- Correlate browser telemetry with web proxy logs to identify visits to pages triggering unusual GPU IPC volume
Monitoring Recommendations
- Enable browser version reporting through enterprise management tooling such as Chrome Browser Cloud Management
- Collect endpoint process telemetry for chrome.exe GPU sub-processes and alert on abnormal crash patterns
- Ingest browser logs into a centralized data lake to enable retrospective hunting once exploit indicators are published
How to Mitigate CVE-2026-95324
Immediate Actions Required
- Update Google Chrome to version 154.0.8037.57 or later on all managed endpoints
- Restart Chrome after the update to ensure the patched GPU process binary is loaded
- Verify Chromium-based browsers (Edge, Brave, Opera, Vivaldi) receive corresponding upstream patches
Patch Information
Google addressed this vulnerability in the Chrome Stable channel release documented in the Google Chrome Stable Update advisory. The fix ships in Chrome 154.0.8037.57 and later. Enterprises using Chrome Browser Cloud Management should confirm auto-update policies are enforced and validate compliance through inventory reports.
Workarounds
- Disable hardware acceleration in Chrome settings to reduce exposure to GPU process code paths until patching completes
- Enforce strict site isolation and block execution of untrusted HTML content through enterprise browser policies
- Restrict browsing to trusted sites via web proxy allow-lists on high-value endpoints
# Verify installed Chrome version on Windows
reg query "HKLM\SOFTWARE\Google\Chrome\BLBeacon" /v version
# Verify installed Chrome version on macOS
defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString
# Verify installed Chrome version on Linux
google-chrome --version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

