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

CVE-2026-113273: Google Chrome ANGLE RCE Vulnerability

CVE-2026-113273 is a memory corruption flaw in Google Chrome ANGLE that enables remote attackers to execute arbitrary code within the sandbox through malicious HTML pages. This article covers technical details, affected versions, security impact, and recommended mitigation strategies.

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

CVE-2026-113273 is a memory corruption vulnerability in ANGLE, the graphics abstraction layer used by Google Chrome to translate OpenGL ES calls to native graphics APIs. The flaw affects Google Chrome versions prior to 156.0.8078.47 and allows a remote attacker to execute arbitrary code inside the browser sandbox through a crafted HTML page. Google classified the Chromium security severity as High. The vulnerability is tracked under CWE-119, covering improper restriction of operations within the bounds of a memory buffer. User interaction is required, since the victim must load attacker-controlled web content.

Critical Impact

Remote attackers can achieve arbitrary code execution inside the Chrome sandbox by luring users to a malicious web page.

Affected Products

  • Google Chrome versions prior to 156.0.8078.47 on desktop platforms
  • Chromium-based browsers that bundle the vulnerable ANGLE component
  • Embedded applications using unpatched Chromium builds for web content rendering

Discovery Timeline

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

Technical Details for CVE-2026-113273

Vulnerability Analysis

The vulnerability resides in ANGLE (Almost Native Graphics Layer Engine), the component Chrome uses to translate WebGL and OpenGL ES commands into platform-specific graphics API calls such as Direct3D, Metal, or Vulkan. A crafted HTML page triggers memory corruption during graphics command processing. An attacker who successfully exploits the flaw gains arbitrary code execution within the renderer process sandbox. While sandbox confinement limits direct host compromise, renderer-level code execution provides a strong foothold for chaining with a sandbox escape to reach the underlying operating system.

Root Cause

The issue is classified as [CWE-119], an improper restriction of operations within the bounds of a memory buffer. The defect occurs inside ANGLE's handling of graphics state or shader resources, where malformed input bypasses expected bounds checks. Public technical details are limited pending broader patch adoption, consistent with Chromium's disclosure practice. See the Chromium Issue Tracker #561999377 for restricted technical details.

Attack Vector

Exploitation requires the victim to visit a malicious or compromised website that serves a crafted HTML page. The page delivers specially shaped WebGL or canvas content that triggers the memory corruption in ANGLE. No credentials are needed, and the attack is deliverable over the network through standard web traffic. Likely delivery channels include phishing links, malvertising, watering-hole compromises, and iframes embedded in trusted sites.

No verified public exploit code is available at this time. For authoritative patch notes, see the Google Chrome Stable Update.

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

Indicators of Compromise

  • Chrome renderer process crashes correlated with visits to untrusted web pages containing WebGL or graphics-heavy content
  • Unexpected child processes spawned from chrome.exe or the renderer helper processes after loading external pages
  • Outbound connections from browser processes to newly observed domains following page loads with heavy graphics activity

Detection Strategies

  • Inventory Chrome installations and flag any host still running a version earlier than 156.0.8078.47
  • Hunt for anomalous child-process creation and memory region allocation patterns originating from Chrome renderer processes
  • Correlate browser crash telemetry with web proxy logs to identify URLs that consistently crash renderers

Monitoring Recommendations

  • Forward Chrome crash reports and endpoint process telemetry to a central analytics platform for cross-host correlation
  • Monitor web proxy and DNS logs for traffic to known malvertising networks and newly registered domains delivering WebGL content
  • Alert on Chrome processes making unusual filesystem writes or loading unsigned modules shortly after page navigation

How to Mitigate CVE-2026-113273

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints across Windows, macOS, and Linux
  • Trigger chrome://settings/help or push the update through enterprise management tooling to force relaunch and apply the patch
  • Audit Chromium-based browsers and embedded WebView components for the vulnerable ANGLE build and update accordingly

Patch Information

Google shipped the fix in the Chrome Stable channel release 156.0.8078.47. Deployment details are documented in the Google Chrome Stable Update. Enterprise administrators should use Chrome Browser Cloud Management, Group Policy, or MDM tooling to enforce the minimum version across the fleet.

Workarounds

  • Restrict access to untrusted sites through web filtering until the patched version is deployed
  • Disable hardware-accelerated graphics in Chrome as a temporary measure where business impact is acceptable, reducing exposure of the ANGLE code path
  • Enforce site isolation and Enhanced Safe Browsing through enterprise policy to raise the cost of exploitation
bash
# Enterprise policy example to enforce minimum Chrome version via Group Policy registry key (Windows)
reg add "HKLM\Software\Policies\Google\Chrome" /v TargetVersionPrefix /t REG_SZ /d "156.0.8078.47" /f
reg add "HKLM\Software\Policies\Google\Chrome" /v RelaunchNotification /t REG_DWORD /d 2 /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.