Skip to main content
Vulnerability Database/CVE-2026-113332

CVE-2026-113332: Google Chrome GPU Memory Corruption RCE

CVE-2026-113332 is a memory corruption vulnerability in Google Chrome GPU that enables remote code execution within the sandbox via malicious HTML pages. This article covers technical details, affected versions, and patches.

Published:

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-113332 Overview

CVE-2026-113332 is a memory corruption vulnerability in the GPU component of Google Chrome prior to version 156.0.8078.47. A remote attacker can execute arbitrary code inside the Chrome sandbox by serving a crafted HTML page to a victim. The flaw is categorized under [CWE-119] (improper restriction of operations within the bounds of a memory buffer). Exploitation requires user interaction, specifically visiting an attacker-controlled page. Google has rated the Chromium security severity as Medium, while the NVD scoring reflects a higher impact rating.

Critical Impact

Successful exploitation grants arbitrary code execution within the Chrome GPU process sandbox, providing attackers a foothold for further sandbox escape chains.

Affected Products

  • Google Chrome Desktop versions prior to 156.0.8078.47
  • Chromium-based browsers inheriting the vulnerable GPU component
  • All platforms (Windows, macOS, Linux) running affected Chrome builds

Discovery Timeline

  • 2026-10-20 - CVE-2026-113332 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-113332

Vulnerability Analysis

The vulnerability resides in Chrome's GPU process, which handles hardware-accelerated rendering, WebGL, WebGPU, and compositing operations. Memory corruption in this component allows an attacker to influence memory contents outside intended buffer boundaries. Because GPU operations process attacker-controlled content from web pages, a crafted HTML document can trigger the corruption during normal rendering. The resulting primitive enables arbitrary code execution confined to the sandboxed GPU process.

The GPU process operates with reduced privileges, but code execution inside it is a common first stage in multi-stage browser exploit chains. Attackers typically pair GPU-process compromise with a separate sandbox escape to reach the host operating system. The vulnerability requires user interaction, limiting mass exploitation but remaining viable through phishing, malvertising, and watering-hole attacks.

Root Cause

The root cause is improper restriction of operations within the bounds of a memory buffer [CWE-119] in Chrome's GPU code. Specific technical details are tracked privately in Chromium Issue Tracker #517031871 and remain restricted pending broader patch adoption.

Attack Vector

The attack vector is network-based through the browser. An attacker hosts a malicious HTML page that triggers the vulnerable GPU code path when rendered. The victim must load the page by clicking a link, viewing a compromised site, or loading a malicious advertisement. No authentication is required. Successful exploitation yields code execution inside the GPU process sandbox.

No verified proof-of-concept code is publicly available. Technical details are described in prose only, pending vendor disclosure. Refer to the Chromium Issue Tracker entry #517031871 for authoritative information once restrictions are lifted.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-113332

Indicators of Compromise

  • Unexpected Chrome GPU process crashes recorded in chrome_debug.log or operating system crash reports
  • Child processes spawned by chrome.exe or the GPU helper process that are not part of normal browser operation
  • Outbound network connections from browser processes to unfamiliar domains following page visits
  • Browser version strings below 156.0.8078.47 reported by endpoint inventory tools

Detection Strategies

  • Inventory installed Chrome versions across managed endpoints and flag any build older than 156.0.8078.47
  • Monitor process trees for anomalous child processes descending from the Chrome GPU process
  • Correlate web proxy logs with endpoint telemetry to identify users visiting suspicious pages followed by browser crashes
  • Alert on repeated GPU process crashes, which may indicate exploitation attempts or fuzzing activity

Monitoring Recommendations

  • Enable browser crash reporting and forward reports to a central SIEM for analysis
  • Track Chrome update compliance through endpoint management platforms and flag deferred updates
  • Monitor DNS and HTTP telemetry for connections to newly registered or low-reputation domains hosting HTML content
  • Review EDR process-execution logs for suspicious activity originating from browser renderer or GPU processes

How to Mitigate CVE-2026-113332

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints
  • Verify Chromium-based browsers (Edge, Brave, Opera, Vivaldi) have adopted the upstream fix
  • Enforce automatic updates through group policy or mobile device management to reduce exposure windows
  • Restart browser instances after patching to ensure the vulnerable code is unloaded from memory

Patch Information

Google released the fix in the Chrome Stable channel at version 156.0.8078.47. Refer to the Google Chrome Stable Update advisory for release notes. Enterprise administrators should deploy the update through standard patch management channels and confirm installation via version reporting.

Workarounds

  • Disable hardware acceleration in Chrome via chrome://settings to reduce exposure to GPU code paths, accepting a performance tradeoff
  • Restrict browser access to untrusted sites through web filtering and DNS reputation services until patching completes
  • Deploy browser isolation technology for high-risk users who cannot be patched immediately
  • Apply the enterprise policy HardwareAccelerationModeEnabled set to false as a temporary control
bash
# Configuration example: disable hardware acceleration via Chrome enterprise policy
# Linux policy file: /etc/opt/chrome/policies/managed/disable_hw_accel.json
{
  "HardwareAccelerationModeEnabled": false
}

# Windows registry equivalent
# HKLM\SOFTWARE\Policies\Google\Chrome
# Value: HardwareAccelerationModeEnabled (DWORD) = 0

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.