CVE-2026-9904: ANGLE Use-After-Free Sandbox Escape in Google Chrome

Technical summary

CVE-2026-9904 is a use-after-free vulnerability (CWE-416) in ANGLE within Google Chrome versions prior to 148.0.7778.216. The vulnerability exists in memory management logic where a graphics object is referenced after it has been freed, creating a dangling pointer condition. An attacker can craft a malicious HTML page that triggers this condition, leading to memory corruption. The vulnerability is particularly dangerous because it can be leveraged to achieve sandbox escape—bypassing Chrome's multi-process isolation model—which allows code execution outside the confined renderer process. The Chromium security team has assigned this a 'High' severity rating.

Business impact

Sandbox escape vulnerabilities represent a significant business risk because they undermine the core security model of modern browsers. An end user visiting a compromised or attacker-controlled website could face complete system compromise without additional user interaction beyond normal browsing. This affects all organizations whose employees use Chrome, including their ability to maintain operational security, protect sensitive data processed in the browser, and defend against supply-chain attacks via malicious web content. Organizations handling sensitive communications, financial transactions, or intellectual property via web applications face elevated risk of data exfiltration or credential theft.

Affected systems

Google Chrome versions prior to 148.0.7778.216 are vulnerable on all operating systems (Windows, macOS, Linux, Chrome OS, and mobile variants). The vulnerability does not require any special browser configuration or extensions; default Chrome installations are at risk. Any user who has not updated to version 148.0.7778.216 or later remains vulnerable to remote exploitation via malicious web content.

Exploitability

This vulnerability requires user interaction—the user must visit a malicious or compromised web page—but the bar for that interaction is low: simply navigating to a crafted URL is sufficient. The attacker does not need to have network connectivity to the target system beyond hosting the malicious HTML page or injecting it into a legitimate website. The complexity is rated as High in the CVSS vector, suggesting the exploit requires precise memory layout conditions or timing, but such constraints do not prevent weaponization by a motivated attacker. The vulnerability is not currently tracked in the CISA KEV catalog, though exploitation is technically feasible. Given the high impact (complete sandbox escape) and the relative ease of delivery, this should be treated as a credible, exploitable threat.

Remediation

Immediately update Google Chrome to version 148.0.7778.216 or later. Chrome typically applies security updates automatically, but users should verify their installed version by navigating to chrome://settings/help and confirming the update has been applied. Organizations should enforce Chrome updates via their device management policies and confirm deployment across all endpoints before considering this issue resolved. No workaround exists for users who cannot immediately update; the only mitigation is to avoid visiting untrusted or unverified web content until the patch is applied.

Patch guidance

Update to Google Chrome 148.0.7778.216 or any subsequent version. Google typically releases security patches on a regular schedule, and this version represents the fix boundary. Verify the patched version by checking chrome://version and confirming the version number matches or exceeds 148.0.7778.216. For enterprise deployments, use your device management platform (MDM, SCCM, or equivalent) to push the update to all Chrome installations. Test the update in a non-production environment first to confirm compatibility with your organization's web applications and extensions. If Chrome auto-update is enabled (the default), most users should already receive this patch; however, forced restarts may be necessary to apply it.

Detection guidance

Monitor for Chrome version compliance across your endpoints using your MDM or vulnerability scanning tools to identify systems running versions prior to 148.0.7778.216. Network-based detection of exploitation attempts is difficult because the payload is embedded in HTML delivered over normal HTTPS traffic; behavioral analytics looking for unusual process creation or elevated privilege operations following web browsing sessions may yield signals. Implement browser isolation technologies or sandboxing solutions for high-risk users to contain any compromise. Monitor system logs for sandbox escape indicators such as renderer processes spawning children outside the sandboxed context. Consider restricting access to untrusted web content via proxy rules or DNS filtering until patch deployment is complete.

Why prioritize this

This vulnerability merits immediate priority due to its combination of high impact (full sandbox escape, arbitrary code execution), low exploitation complexity from the user's perspective (visiting a web page), and broad affected population (all Chrome users). The ability to escape the browser sandbox elevates this from a renderer-process compromise to a full system compromise. Unlike vulnerabilities requiring user-password entry or special permissions, this requires only passive web browsing. Organizations should deprioritize lower-severity patching tasks and focus on Chrome updates immediately.

Risk score, explained

The CVSS 3.1 score of 8.3 (HIGH) reflects a network-based attack vector, high impact across confidentiality, integrity, and availability, and high complexity—typical of memory corruption exploits. The presence of a user interaction requirement (visiting a malicious page) prevents a perfect 9.0+ score, and the attack complexity being 'High' suggests the exploit is not trivial to develop. However, the scope change from Unchanged to Changed (the 'C' in CVSS indicates cross-boundary impact—sandbox escape) pushes the score higher. In practice, real-world exploitation may be more feasible than the CVSS complexity suggests, warranting aggressive patching.

Frequently asked questions