CVE-2026-9899: Chrome ANGLE Use-After-Free Sandbox Escape (CVSS 8.3)

Technical summary

CVE-2026-9899 is a use-after-free vulnerability (CWE-416) in the ANGLE graphics library integrated into Google Chrome. The flaw exists in memory management within the renderer process; an attacker who has already achieved code execution in that sandboxed context can trigger the use-after-free to corrupt memory and potentially pivot to a sandbox escape. The vulnerability carries a CVSS 3.1 score of 8.3 (High severity) with a vector reflecting network attack surface, high complexity, user interaction requirement, and ability to compromise confidentiality, integrity, and availability. Google rates this as High chromium security severity.

Business impact

A successful exploit chain—first compromising the renderer, then escaping the sandbox—would give an attacker unrestricted access to the underlying system. This could lead to data exfiltration, malware installation, lateral movement, or supply-chain compromise if the user's system is part of a managed enterprise environment. Organizations with users who browse untrusted websites face elevated risk.

Affected systems

Google Chrome versions prior to 148.0.7778.216 are affected. Users on older versions remain vulnerable until they upgrade. The vulnerability is specific to the ANGLE graphics library as implemented in Chrome; other Chromium-based browsers may be affected depending on their use of the same ANGLE code, though those are outside the scope of this CVE.

Exploitability

Exploitation is feasible but not trivial. An attacker must first compromise Chrome's renderer process—typically via a separate browser vulnerability or social engineering—and then use CVE-2026-9899 to break out of the sandbox. The attack requires a crafted HTML page and user interaction, making opportunistic mass exploitation less likely than targeted attacks. The vulnerability does not appear on the CISA Known Exploited Vulnerabilities catalog, indicating no widespread active exploitation has been publicly confirmed as of the modification date.

Remediation

Update Google Chrome to version 148.0.7778.216 or later. Chrome's auto-update mechanism typically deploys patches within days; users should verify they are running the latest version via Settings > About Chrome. Enterprise environments should verify patch deployment via their device management policies.

Patch guidance

Upgrade to Google Chrome 148.0.7778.216 or any subsequent stable release. Verify the installed version in Settings > About Chrome; the browser will automatically download and apply the patch on next restart if available. Enterprise deployments should verify successful rollout through their mobile device management (MDM) or endpoint management console within one week of patch release. No interim workarounds are available; patching is the only mitigation.

Detection guidance

Monitor for unusual process behavior following Chrome renderer crashes or high memory churn, which may indicate exploitation attempts. Endpoint detection and response (EDR) tools should flag attempts to spawn system processes or access sensitive data immediately after Chrome crashes or exhibits memory corruption. However, detection is challenging because exploitation occurs within the browser's sandboxed process; focus on behavioral anomalies post-crash rather than the vulnerability itself. Web proxy logs showing delivery of crafted HTML pages to users can provide indirect signals if correlated with device incidents.

Why prioritize this

Patch this vulnerability promptly because successful exploitation enables full sandbox escape—moving from renderer-level compromise to system-level access. Although the initial renderer compromise is a prerequisite, organizations cannot assume their users will never encounter malicious content; the sandbox escape capability elevates the overall risk. The High CVSS score and Chromium security severity designation reflect this threat escalation. Prioritize patching for systems in high-value roles (developers, analysts, administrators) and endpoints in sensitive network segments.

Risk score, explained

The CVSS 8.3 (High) score reflects: (1) network attack surface (AV:N) via crafted web content, (2) high attack complexity (AC:H) due to the need for prior renderer compromise and specific trigger conditions, (3) no privileges required from the attacker once renderer access is gained (PR:N), (4) user interaction needed (UI:R) to visit the malicious page, and (5) changed security scope (S:C) with high impact on confidentiality, integrity, and availability. The score appropriately weights the severity of sandbox escape against the relative difficulty of exploitation.

Frequently asked questions