CVE-2026-9877: Chrome Use-After-Free in ANGLE Graphics Library Enables Sandbox Escape

Technical summary

CVE-2026-9877 is a use-after-free vulnerability (CWE-416) in ANGLE, the Almost Native Graphics Layer Engine used by Chrome for hardware-accelerated graphics rendering. The flaw occurs when freed memory is accessed after deallocation, potentially leading to control flow hijacking or arbitrary code execution. An attacker with renderer process compromise can trigger this condition via crafted HTML, bypassing Chrome's sandbox isolation layer that normally restricts renderer access to system resources. The CVSS 3.1 score of 8.3 (HIGH) reflects high impact across confidentiality, integrity, and availability, though exploitation requires initial renderer compromise and user interaction.

Business impact

Successful exploitation enables complete system compromise following browser exploitation, allowing threat actors to move beyond the sandboxed renderer to access user data, install malware, or pivot to other systems. Organizations with users on affected Chrome versions face elevated risk of targeted attacks combining web-based exploits with sandbox escapes. The impact extends beyond Chrome users to Windows, macOS, and Linux systems across all platforms where Chrome operates.

Affected systems

Google Chrome versions prior to 148.0.7778.216 are vulnerable. The vulnerability affects Chrome installations on Microsoft Windows, Apple macOS, and Linux systems. Any organization running unpatched Chrome on these platforms—particularly in environments where users visit untrusted or attacker-controlled websites—is at risk.

Exploitability

Exploitation requires two prerequisites: (1) the renderer process must already be compromised, typically through a separate browser vulnerability or malicious website, and (2) the user must interact with the crafted HTML page. The vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities catalog, indicating active exploitation in the wild has not been confirmed at the time of publication. However, the sandbox escape capability makes this an attractive post-compromise objective for sophisticated threat actors.

Remediation

Update Google Chrome to version 148.0.7778.216 or later. Chrome's auto-update mechanism should deploy patches automatically for most users, but organizations should verify completion in their environments. No workarounds exist; patching is the only mitigation. Users unable to update immediately should disable untrusted content and restrict web browsing to known-safe sites.

Patch guidance

Deploy Chrome 148.0.7778.216 or later across your organization. Verify the update through Chrome's About menu (chrome://about), which displays current version and update status. For enterprise deployments using Chrome policy, update your policy-managed Chrome instances and confirm rollout completion within 48 hours. Organizations with auto-update enabled should see patches deployed within days of release.

Detection guidance

Monitor Chrome processes for crash reports or abnormal termination, which may indicate exploitation attempts. Endpoint detection systems should flag unusual GPU/ANGLE library access patterns or unexpected child process spawning from chrome.exe/chromium processes, as sandbox escapes typically manifest as privilege escalation attempts. Log authentication and file access anomalies on systems following Chrome crashes or restarts. Network-based detection of the exploit itself is not practical; focus on post-exploitation behavioral signals.

Why prioritize this

Despite being unconfirmed in active exploitation, this vulnerability merits urgent priority due to its sandbox escape capability combined with critical severity rating from Chromium. The attack chain—website compromise leading to renderer compromise leading to full system compromise—is practical and attractive to nation-state and advanced criminal threat actors. Organizations should treat this as a critical patch within their Chrome fleet.

Risk score, explained

The CVSS 3.1 score of 8.3 reflects high impact (confidentiality, integrity, availability all marked as high) balanced against the attack complexity and prerequisite (AC:H, PR:N requiring renderer compromise via UI interaction). While not a base-level 9.0+, the sandbox escape itself elevates risk substantially above typical renderer vulnerabilities because it bypasses the primary Chrome security boundary. Absence from the KEV catalog does not lower priority given the exploit's sophistication and post-compromise value.

Frequently asked questions