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-113295 Overview
CVE-2026-113295 is an out-of-bounds read vulnerability in the ANGLE (Almost Native Graphics Layer Engine) component of Google Chrome on Windows. The flaw affects Chrome versions prior to 156.0.8078.47 and allows a remote attacker to read memory inside the Chrome sandbox using a crafted HTML page. ANGLE translates OpenGL ES API calls into DirectX, OpenGL, or Vulkan calls, and it is reachable from untrusted web content through WebGL. The weakness is classified under [CWE-125: Out-of-bounds Read]. Google rated the Chromium security severity as High, while the NVD CVSS score is 6.5 (Medium).
Critical Impact
A remote attacker can leak sensitive memory contents from inside the Chrome sandbox by convincing a user to load a malicious HTML page, potentially exposing data useful for further exploitation.
Affected Products
- Google Chrome on Windows prior to 156.0.8078.47
- Microsoft Windows (host operating system)
- Chromium-based browsers that embed vulnerable ANGLE builds
Discovery Timeline
- 2026-10-20 - CVE-2026-113295 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113295
Vulnerability Analysis
The vulnerability resides in ANGLE, Chrome's graphics abstraction layer that translates WebGL and OpenGL ES calls into native GPU API calls on Windows. An out-of-bounds read occurs when ANGLE accesses memory outside the bounds of an allocated buffer during the handling of attacker-controlled graphics data. Because WebGL exposes ANGLE to any origin that renders a canvas, a remote attacker can trigger the condition by serving a crafted HTML page.
The read is confined to the renderer sandbox, which is why user interaction is required and integrity and availability remain unaffected. However, leaking memory from the renderer process can disclose pointers, tokens, and other sensitive data that defeats address space layout randomization (ASLR) and supports chaining with a sandbox escape.
Root Cause
The root cause is missing or incorrect bounds validation inside an ANGLE code path that processes graphics input. When the component indexes a buffer using attacker-influenced values, it reads past the valid allocation. The weakness maps to [CWE-125] and is characteristic of complex, performance-sensitive graphics translation code paths.
Attack Vector
Exploitation is remote and occurs over the network. The attacker hosts a malicious page containing crafted WebGL or ANGLE-reachable content, then lures a user to visit it. When the page renders, Chrome's GPU/renderer pipeline invokes the vulnerable ANGLE routine and returns memory contents to the attacker-controlled JavaScript context. No authentication is required, and the attack is scoped to the sandbox.
No public proof-of-concept, exploit code, or CISA KEV listing is associated with CVE-2026-113295 at the time of publication. The EPSS probability is 0.301%.
Detection Methods for CVE-2026-113295
Indicators of Compromise
- Chrome renderer or GPU process crashes referencing ANGLE modules such as libGLESv2.dll or libEGL.dll
- Browser telemetry showing Chrome versions below 156.0.8078.47 on Windows endpoints
- Outbound connections from browser processes to newly registered or low-reputation domains delivering WebGL-heavy content
Detection Strategies
- Inventory installed Chrome builds across the fleet and flag any Windows host running a version earlier than 156.0.8078.47
- Correlate Windows Error Reporting (WER) and crash dumps for faulting modules associated with ANGLE in the Chrome process tree
- Monitor for unusual child-process or memory-access patterns originating from chrome.exe renderer processes after visits to untrusted sites
Monitoring Recommendations
- Ingest endpoint browser version data into a SIEM or data lake and alert on hosts missing the fixed build
- Enable web proxy or DNS logging to identify users retrieving suspicious HTML pages that heavily exercise WebGL
- Track Chrome auto-update health to confirm the patched version propagates within the organization's defined SLA
How to Mitigate CVE-2026-113295
Immediate Actions Required
- Update Google Chrome on all Windows endpoints to version 156.0.8078.47 or later
- Restart browsers after the update to ensure the patched ANGLE libraries are loaded
- Verify that Chromium-based browsers (Edge, Brave, Opera, Vivaldi) receive their vendor's corresponding ANGLE update
Patch Information
Google addressed CVE-2026-113295 in the Chrome Stable channel release documented in the Google Chrome Stable Update advisory. Additional technical context is tracked in the Chromium Issue Tracker #568897206. Administrators should confirm clients report build 156.0.8078.47 or newer under chrome://settings/help.
Workarounds
- Disable hardware acceleration in Chrome under Settings to reduce exposure of the ANGLE code path until patching completes
- Use enterprise policy to block or restrict WebGL on untrusted sites via the DefaultWebGLSetting or site-isolation policies
- Restrict user browsing to trusted sites through proxy or DNS filtering for high-risk user populations
# Configuration example: enforce minimum Chrome version via Windows Group Policy registry
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 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

