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

CVE-2026-113134: Google Chrome ANGLE RCE Vulnerability

CVE-2026-113134 is a memory corruption flaw in ANGLE component of Google Chrome on Windows that enables remote code execution within the sandbox. This post explains the technical details, affected versions, and mitigation steps.

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

CVE-2026-113134 is a memory corruption vulnerability in the ANGLE (Almost Native Graphics Layer Engine) component of Google Chrome on Windows. A remote attacker can execute arbitrary code inside the Chrome sandbox by serving a crafted HTML page to a target user. The flaw affects Chrome versions prior to 156.0.8078.47 and requires user interaction, such as visiting an attacker-controlled page. Google rated the Chromium security severity as High, and the vulnerability is categorized under CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer.

Critical Impact

Successful exploitation enables arbitrary code execution inside the Chrome sandbox on Windows endpoints via a single crafted web page.

Affected Products

  • Google Chrome for Windows versions prior to 156.0.8078.47
  • ANGLE graphics abstraction layer bundled with affected Chrome builds
  • Chromium-based browsers on Windows that embed the vulnerable ANGLE component

Discovery Timeline

  • 2026-10-20 - CVE-2026-113134 published to the National Vulnerability Database
  • 2026-10-21 - Last updated in the NVD database

Technical Details for CVE-2026-113134

Vulnerability Analysis

The vulnerability resides in ANGLE, the graphics abstraction layer Chrome uses on Windows to translate OpenGL ES calls into Direct3D operations. A memory corruption condition in ANGLE allows a crafted HTML page containing malicious WebGL or graphics content to corrupt process memory within the Chrome renderer or GPU process. The attack vector is network-based and requires the victim to load the attacker's page. Exploitation yields arbitrary code execution confined to the Chrome sandbox, which an attacker can then chain with a sandbox escape to achieve full host compromise.

Root Cause

The weakness is classified as [CWE-119], an improper restriction of operations within the bounds of a memory buffer. Public details are limited while the Chromium issue remains restricted, but the defect is located in ANGLE's handling of graphics API inputs on Windows builds of Chrome. Processing of attacker-controlled graphics state leads to an out-of-bounds memory operation that corrupts adjacent structures and can be steered toward control-flow hijacking.

Attack Vector

An attacker hosts a crafted HTML page that triggers the vulnerable ANGLE code path when rendered by a vulnerable Chrome version. No authentication is required, and attack complexity is low, but the victim must open the malicious URL. Common delivery methods include phishing links, malvertising, watering-hole compromises, and injected content in third-party iframes. Successful execution runs attacker code inside the sandboxed renderer or GPU process, enabling further exploitation stages.

No public proof-of-concept exploit or in-the-wild exploitation has been confirmed. See the Chromium Issue Tracker #560423758 and the Google Chrome Desktop Update for vendor-provided technical context.

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-113134

Indicators of Compromise

  • Unexpected crashes of chrome.exe renderer or GPU processes referencing libGLESv2.dll or libEGL.dll (ANGLE libraries) in Windows Error Reporting data.
  • Chrome child processes spawning command interpreters such as cmd.exe or powershell.exe immediately after a browsing session.
  • Outbound connections from Chrome processes to newly registered or low-reputation domains serving WebGL-heavy content.

Detection Strategies

  • Hunt for anomalous process trees where chrome.exe renderer or GPU processes create child processes or write executables to disk.
  • Correlate browser crash telemetry with the ANGLE modules to surface potential exploitation attempts prior to full compromise.
  • Inspect web proxy and DNS logs for pages that aggressively load WebGL contexts from untrusted origins.

Monitoring Recommendations

  • Deploy EDR rules that alert on Chrome GPU or renderer processes performing memory allocation patterns consistent with shellcode staging.
  • Track installed Chrome versions across Windows endpoints and alert on any build earlier than 156.0.8078.47.
  • Review Windows crash dumps for recurring faults inside ANGLE translation routines, which may indicate exploitation attempts.

How to Mitigate CVE-2026-113134

Immediate Actions Required

  • Update Google Chrome on Windows to version 156.0.8078.47 or later across all managed endpoints.
  • Force a browser restart after update deployment to ensure the patched ANGLE libraries are loaded.
  • Audit Chromium-derived browsers (Edge, Brave, Opera, Vivaldi) and apply vendor updates that incorporate the ANGLE fix.

Patch Information

Google addressed the issue in the Chrome Stable channel release documented in the Google Chrome Desktop Update. Install Chrome 156.0.8078.47 or later. Enterprises using managed Chrome deployments should push the update through Group Policy, Chrome Browser Cloud Management, or their endpoint management platform.

Workarounds

  • Where immediate patching is not possible, disable hardware acceleration in Chrome to reduce exposure to ANGLE code paths, accepting the performance trade-off.
  • Restrict browsing to trusted sites using enterprise URL allowlists and block WebGL content from untrusted origins via browser policy.
  • Apply site isolation and strict sandbox settings via Chrome Enterprise policies to limit the blast radius of renderer compromise.
bash
# Verify installed Chrome version on Windows endpoints (PowerShell)
(Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion

# Example Chrome Enterprise policy to disable hardware acceleration (registry)
reg add "HKLM\Software\Policies\Google\Chrome" /v HardwareAccelerationModeEnabled /t REG_DWORD /d 0 /f

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.