CVE-2026-10889: Critical ANGLE Sandbox Escape in Google Chrome – Patch to 149.0.7827.53

Technical summary

CVE-2026-10889 is an out-of-bounds read vulnerability in ANGLE (Almost Native Graphics Layer Engine), the graphics abstraction layer used by Google Chrome. The flaw is triggered when processing malformed graphics commands via a crafted HTML page. An attacker who has already compromised the Chrome renderer process can exploit this to read memory outside allocated buffers, potentially leaking sensitive data or crafting further exploits. The vulnerability enables sandbox escape, meaning code executing in the restricted renderer context can break containment and execute with the privileges of the host operating system. This is classified as CWE-125 (Out-of-bounds Read), and Google assessed it as Critical severity at the Chromium level.

Business impact

This vulnerability represents a critical escalation risk in multi-stage attacks. While it requires the attacker to first compromise the renderer process (via malicious script injection, malicious ad delivery, or drive-by download), the sandbox escape capability means secondary malware deployed through this path gains system-level access without user elevation prompts. Organizations heavy on browser-based workflows face risk of data exfiltration, lateral movement, and persistence mechanisms planted at the OS level. The attack surface is broad because it only requires a user to visit a malicious or compromised website.

Affected systems

Google Chrome prior to version 149.0.7827.53 is directly affected. The vulnerability impacts Chrome on Windows, macOS, and Linux distributions. Web browsers on these operating systems and any Chromium-based browsers (Edge, Opera, Brave, etc.) that have not applied equivalent patches may also be vulnerable, though official patch guidance should be verified for each vendor. iOS and Android Chrome may have separate patch schedules.

Exploitability

Exploitation requires two prerequisites: first, an attacker must successfully compromise the Chrome renderer process (via script injection, malicious content, or similar vector), and second, the victim must view a page containing the crafted exploit payload. The CVSS vector reflects high impact but intermediate attack complexity due to these prerequisites. While the barrier to initial renderer compromise exists, the subsequent sandbox escape is reliable once triggered, making this particularly dangerous in targeted or high-volume campaign scenarios. No public exploit code is known to be in active use as of the advisory publication.

Remediation

Immediately update Google Chrome to version 149.0.7827.53 or later. For Chromium-based browsers and derivative products, consult vendor advisories for equivalent patch versions. Organizations using managed Chrome deployments should push updates via device management policies. Verify patch deployment before assuming protection, as ANGLE is a core graphics component and requires full browser restart to load patched code. Consider temporary browser usage restrictions for high-risk users pending patch deployment.

Patch guidance

Google Chrome updates are typically deployed automatically, but users and administrators should verify installation by navigating to chrome://settings/help, which will display the current version and trigger update checks. Patches typically roll out over several days; expedited deployment through enterprise policy (Chrome Enterprise or similar) may be necessary for sensitive environments. Test patch compatibility with any organization-specific browser extensions or policies before broad rollout. Ensure users restart their browser fully; simply closing tabs does not unload the vulnerable ANGLE library. For unmanaged environments, educate users to enable automatic updates and restart when prompted.

Detection guidance

Monitor for indicators of renderer process compromise as a precursor: look for suspicious JavaScript execution, unexpected process spawning from Chrome, or unusual system calls from chrome.exe/chrome processes. Post-compromise, detect sandbox escape attempts by monitoring for process privilege escalation events, creation of child processes with SYSTEM or administrator tokens from browser-spawned processes, and file access outside expected browser directories. EDR/XDR platforms should alert on out-of-bounds memory access patterns and graphics driver anomalies. Network detection is limited since the exploit is local once renderer is compromised; focus on command-and-control beaconing or lateral movement that follows sandbox escape. Log Chrome renderer crashes, which may indicate failed exploitation attempts.

Why prioritize this

Assign this vulnerability high priority for immediate patching. Although it requires prior renderer compromise, sandbox escape vulnerabilities are strategically valuable in advanced attacks because they eliminate a key security boundary. Organizations should prioritize Chrome patch deployment above routine updates. The attack surface spans any internet-connected user on Windows, macOS, or Linux; widespread deployment of Chrome elevates organizational risk. While not yet in active exploitation at scale, the combination of ease-of-use and system-level impact makes it attractive to motivated threat actors.

Risk score, explained

The CVSS 3.1 score of 8.3 (HIGH) reflects high confidentiality, integrity, and availability impact due to the sandbox escape capability, but is tempered by moderate attack complexity (the renderer must first be compromised) and requirement for user interaction. The score does not capture the full strategic risk of sandbox escape—which from a defense perspective is often more critical than the individual CVSS number suggests. An organization's actual risk depends heavily on whether users regularly visit untrusted websites and on the maturity of endpoint detection and response (EDR) capabilities.

Frequently asked questions