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-95331 Overview
CVE-2026-95331 is an out-of-bounds write vulnerability [CWE-787] in ANGLE, the graphics abstraction layer used by Google Chrome. The flaw affects Chrome versions prior to 154.0.8037.57. A remote attacker can exploit it by serving a crafted HTML page to a victim. Successful exploitation may execute arbitrary code outside the Chrome sandbox, breaking one of the browser's primary defensive boundaries.
Google rated the underlying Chromium security severity as Medium, but the NVD scoring reflects the sandbox escape potential and network-based attack vector.
Critical Impact
Remote attackers can achieve arbitrary code execution outside the Chrome sandbox through a crafted web page, requiring only that a user visit the malicious content.
Affected Products
- Google Chrome for Desktop versions prior to 154.0.8037.57
- ANGLE graphics component shipped within Chromium
- Chromium-based browsers that embed the vulnerable ANGLE version
Discovery Timeline
- 2026-09-29 - CVE-2026-95331 published to the National Vulnerability Database
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-95331
Vulnerability Analysis
The defect resides in ANGLE (Almost Native Graphics Layer Engine), the component that translates OpenGL ES API calls into native graphics API calls such as Direct3D, Metal, or Vulkan. ANGLE runs inside the Chrome GPU process, which historically has weaker sandbox constraints than the renderer process because it requires direct hardware access.
An out-of-bounds write occurs when the component writes data past the boundaries of an allocated buffer. In ANGLE, such conditions typically arise while processing WebGL commands, shader inputs, or texture data supplied from a renderer. Because the corrupted memory sits inside the GPU process, successful memory manipulation can bypass the renderer sandbox entirely.
Refer to the Chromium Issue Tracker #500127519 and the Google Chrome Desktop Update for the vendor advisory.
Root Cause
The root cause is missing or insufficient bounds checking on data processed inside ANGLE. Attacker-influenced values written outside the intended buffer overwrite adjacent memory structures, enabling control over program state.
Attack Vector
Exploitation is network-based and requires user interaction. The attacker hosts a crafted HTML page containing malicious WebGL or graphics content. When a victim visits the page, ANGLE processes the attacker-controlled input and the out-of-bounds write triggers memory corruption inside the GPU process. No authentication is required, and the scope changes because compromise moves from the renderer sandbox into the more privileged GPU process context.
No verified exploit code is publicly available for this vulnerability. See the referenced Chromium advisory for 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 AttemptsDetection Methods for CVE-2026-95331
Indicators of Compromise
- Unexpected child processes spawned from chrome.exe GPU processes, particularly command interpreters or scripting hosts
- GPU process crashes correlated with visits to untrusted web content
- Outbound network connections initiated by Chrome GPU process to previously unseen infrastructure
- Chrome versions running below 154.0.8037.57 reported by endpoint inventory
Detection Strategies
- Monitor for anomalous process lineage where Chrome GPU processes create non-graphics child processes
- Correlate browser crash telemetry with subsequent suspicious execution on the same host
- Track browser version compliance across managed endpoints and flag hosts running vulnerable Chrome builds
Monitoring Recommendations
- Ingest browser telemetry and process events into a centralized data lake for retrospective hunting
- Alert on Chrome GPU process memory access violations followed by persistence or lateral movement activity
- Review web proxy logs for user visits to newly registered or low-reputation domains preceding browser crashes
How to Mitigate CVE-2026-95331
Immediate Actions Required
- Update Google Chrome to version 154.0.8037.57 or later on all managed endpoints
- Restart browser instances after patching to ensure the vulnerable ANGLE component is unloaded
- Audit Chromium-based browsers such as Edge, Brave, and Opera and apply their upstream patched builds
Patch Information
Google released the fix in Chrome Stable channel version 154.0.8037.57. Details are published in the Google Chrome Desktop Update release notes. Enterprise administrators should push the update through managed software distribution.
Workarounds
- Disable hardware acceleration in Chrome to reduce reliance on the ANGLE code path where operationally acceptable
- Restrict WebGL usage through enterprise policy on high-risk endpoints until patching completes
- Enforce site isolation and block navigation to untrusted domains via web filtering
# Enterprise policy example to disable hardware acceleration on Windows
# Registry path: HKLM\Software\Policies\Google\Chrome
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

