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-113143 Overview
CVE-2026-113143 is a memory corruption vulnerability in the ANGLE (Almost Native Graphics Layer Engine) component of Google Chrome. ANGLE translates OpenGL ES API calls into native graphics API calls for the host platform. The flaw affects Chrome versions prior to 156.0.8078.47. A remote attacker can read process memory by serving a crafted HTML page to a target user. The weakness is tracked under CWE-119, covering improper restriction of operations within memory buffer bounds.
Critical Impact
A remote attacker can trigger out-of-bounds memory access through a crafted web page, enabling disclosure of browser process memory contents.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- ANGLE graphics abstraction component in Chromium
- Downstream Chromium-based browsers that have not integrated the Chrome 156 security update
Discovery Timeline
- 2026-10-20 - CVE-2026-113143 published to the National Vulnerability Database
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113143
Vulnerability Analysis
The vulnerability resides in ANGLE, the graphics engine Chrome uses to translate WebGL and OpenGL ES calls to the underlying platform graphics stack. Improper bounds handling in ANGLE allows a remote attacker to coerce the renderer into reading memory outside intended buffer limits.
An attacker-controlled HTML page can issue crafted WebGL commands that drive ANGLE into the vulnerable code path. The resulting out-of-bounds read can disclose adjacent memory, which may contain sensitive data such as pointers, tokens, or content from other origins. Google categorized the Chromium security severity as Medium, while NVD assigned a higher CVSS base score reflecting network reachability and user interaction only through visiting a page.
The issue is referenced in the Chromium Issue Tracker and addressed in the Chrome Stable channel update.
Root Cause
The root cause is improper restriction of operations within the bounds of a memory buffer inside ANGLE. Specific input sequences cause the component to access memory outside the intended allocation, categorized under [CWE-119]. Google has not published source-level technical details while the fix propagates to downstream distributions.
Attack Vector
Exploitation requires a user to visit a malicious or compromised web page in a vulnerable Chrome build. No authentication or special privileges are needed. The crafted page issues WebGL or related graphics API calls that reach the vulnerable ANGLE path. Successful exploitation leaks memory from the renderer process to the attacker-controlled page, enabling further reconnaissance or chaining with other browser flaws.
No public proof-of-concept, exploit, or CISA KEV listing exists for this CVE at publication time.
Detection Methods for CVE-2026-113143
Indicators of Compromise
- Browser renderer process crashes or GPU process restarts correlated with visits to untrusted sites
- Outbound HTTP(S) connections to recently registered domains serving pages with heavy WebGL content
- Chrome telemetry or crash dumps referencing ANGLE modules such as libGLESv2 or ANGLE-translated shader paths
Detection Strategies
- Inventory endpoints running Chrome builds older than 156.0.8078.47 through endpoint management or EDR software inventory
- Monitor browser version strings reported via user-agent headers at web proxies to flag outdated clients
- Correlate web proxy logs with threat intelligence feeds that identify malicious WebGL exploit pages
Monitoring Recommendations
- Enable Chrome crash and stability reporting to central telemetry for anomaly review
- Track GPU process termination events on Windows, macOS, and Linux endpoints
- Alert on repeated renderer sandbox violations originating from the same browsing session
How to Mitigate CVE-2026-113143
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints
- Force a browser restart through enterprise management to ensure the patched binary is loaded
- Audit Chromium-based browsers (Edge, Brave, Opera, Vivaldi) for availability of the equivalent ANGLE fix
Patch Information
Google released the fix in Chrome Stable channel version 156.0.8078.47. See the Chrome Desktop Update Announcement for details. Administrators should deploy the update through Google Update, enterprise MDM, or package management, then verify installed versions across the fleet.
Workarounds
- Restrict access to untrusted websites using web filtering or DNS policy until patches are deployed
- Disable hardware acceleration via chrome://settings or the HardwareAccelerationModeEnabled enterprise policy to reduce ANGLE code path exposure
- Enforce Chrome auto-update policies through Group Policy or MDM to prevent version drift
# Verify installed Chrome version on Windows via PowerShell
(Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
# Verify installed Chrome version on macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# 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

