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-113163 Overview
CVE-2026-113163 is a use-after-free vulnerability in the WebGL component of Google Chrome on Android. The flaw affects versions prior to 156.0.8078.47 and allows a remote attacker to execute arbitrary code inside the Chrome sandbox through a crafted HTML page. Google classified the Chromium security severity as High. Exploitation requires user interaction, specifically visiting a malicious or compromised web page. The vulnerability is tracked under CWE-416: Use After Free.
Critical Impact
A remote attacker can execute arbitrary code within the Chrome renderer sandbox on Android devices by luring a user to a crafted HTML page.
Affected Products
- Google Chrome for Android versions prior to 156.0.8078.47
- Chromium-based browsers on Android that embed the vulnerable WebGL implementation
- Android applications using Chrome WebView builds derived from affected Chromium releases
Discovery Timeline
- 2026-10-20 - CVE-2026-113163 published to the National Vulnerability Database
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113163
Vulnerability Analysis
The vulnerability resides in the WebGL implementation of Chrome on Android. WebGL (Web Graphics Library) exposes GPU-accelerated rendering APIs to JavaScript running inside the browser. A use-after-free condition in this component means a WebGL object is freed while a reference to its memory remains reachable, and subsequent operations dereference the stale pointer.
An attacker who controls a page can shape heap layout and trigger the dangling reference, then reuse the freed slot to achieve controlled memory corruption. Successful exploitation yields arbitrary code execution inside the renderer process. Code runs within the Chrome sandbox, so a second escape primitive would be required to reach the underlying Android system. The flaw requires user interaction, which maps to a victim visiting an attacker-controlled page.
Root Cause
The root cause is improper object lifetime management inside the WebGL graphics stack ([CWE-416]). A WebGL-related object is released while JavaScript or internal GPU command processing retains a reference. When that reference is used again, the browser operates on reclaimed memory that an attacker can groom with controlled data. Specific technical details are tracked in Chromium Issue Tracker #548066294.
Attack Vector
Exploitation is network-based and requires no privileges. The attacker hosts a crafted HTML page that loads malicious WebGL shaders, buffers, or draw-call sequences through JavaScript. The victim must visit the page using a vulnerable Chrome build on Android. Delivery vectors include phishing links, malicious advertisements, compromised sites, and embedded WebViews. See the Google Chrome Stable Update advisory for release details.
No public proof-of-concept is listed in the available references, and the vulnerability is not present on the CISA Known Exploited Vulnerabilities catalog at the time of publication.
Detection Methods for CVE-2026-113163
Indicators of Compromise
- Chrome for Android clients still running versions below 156.0.8078.47 after the patch release date
- Unexpected renderer process crashes on Android devices correlated with WebGL-heavy page loads
- Outbound connections from mobile endpoints to newly registered domains serving pages with large or obfuscated WebGL shader payloads
Detection Strategies
- Inventory Chrome and Chromium-based browser versions across managed Android devices and flag builds older than 156.0.8078.47
- Inspect mobile web proxy logs for HTML pages invoking heavy use of WebGLRenderingContext, WebGL2RenderingContext, or rapid buffer allocation patterns from untrusted origins
- Correlate Android crash telemetry referencing GPU or renderer processes with recent navigation history to identify suspicious pages
Monitoring Recommendations
- Enable browser version telemetry through mobile device management (MDM) and alert on out-of-date Chrome installations
- Monitor for Android WebView components bundled by third-party apps that remain pinned to vulnerable Chromium builds
- Track threat intelligence feeds for domains distributing WebGL-based renderer exploits targeting Android
How to Mitigate CVE-2026-113163
Immediate Actions Required
- Update Google Chrome on Android to version 156.0.8078.47 or later through the Google Play Store
- Push forced Chrome updates to managed Android devices using MDM configuration policies
- Audit in-house Android applications for embedded Chromium or WebView components and rebuild them against the patched release
Patch Information
Google addressed the issue in the Chrome Stable channel. Users and administrators should install Chrome for Android 156.0.8078.47 or newer. Full release details are available in the Google Chrome Stable Update announcement, and tracking metadata is maintained in Chromium Issue Tracker #548066294.
Workarounds
- Restrict access to untrusted websites on managed Android devices until all browsers are patched
- Disable WebGL where feasible on sensitive devices by using enterprise browser policies that limit hardware-accelerated graphics for untrusted origins
- Apply network-level filtering to block known malicious domains and advertising networks that could serve crafted WebGL payloads
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

