CVE-2026-9914: Chrome ANGLE Sandbox Escape Vulnerability (CVSS 8.3)

Technical summary

CVE-2026-9914 is a sandbox escape vulnerability in ANGLE (Almost Native Graphics Layer Engine) within Google Chrome versions prior to 148.0.7778.216. The vulnerability arises from insufficient input validation (CWE-20) in how ANGLE processes untrusted data. An attacker who has already compromised the renderer process can leverage a specially crafted HTML page to trigger the vulnerability and potentially escape the sandbox, gaining elevated execution context. The CVSS 3.1 score of 8.3 (High) reflects the requirement for initial renderer compromise while acknowledging the severe impact of a successful sandbox escape.

Business impact

A successful exploitation allows an attacker to move beyond the renderer sandbox—the critical isolation layer that confines malicious content. Once outside the sandbox, an attacker gains access to sensitive user data, browser functionality, and potentially the underlying operating system, creating risk for credential theft, malware installation, and lateral movement. For organizations, this elevates Chrome security incidents from contained browser exploitation to potential full system compromise.

Affected systems

Google Chrome versions prior to 148.0.7778.216 are vulnerable. This includes desktop and mobile deployments of Chrome that have not received the security update. Users running Chrome 148.0.7778.216 or later are protected. Chromium-based browsers built from vulnerable source versions may also be affected; verify with your specific browser vendor.

Exploitability

Exploitation requires two preconditions: (1) the renderer process must already be compromised, and (2) the user must interact with a crafted HTML page. While the renderer compromise typically requires a separate vulnerability (such as a browser engine flaw), the sandbox escape itself has high impact once those conditions are met. The CVSS vector reflects this via High complexity (AC:H) and the requirement for user interaction (UI:R), though the attack is network-based (AV:N) and produces cascading impact across confidentiality, integrity, and availability (S:C).

Remediation

Update Google Chrome to version 148.0.7778.216 or later. Chrome's auto-update mechanism will deploy this patch automatically for most users; verify completion by navigating to chrome://settings/help or the equivalent on your platform. Organizations using managed Chrome deployments should verify patch deployment through their policy management console and confirm rollout to all endpoints before deprioritizing this issue.

Patch guidance

Apply Chrome 148.0.7778.216 or any subsequent version. For managed environments, use your Chrome Enterprise policy management tools to enforce the update and confirm compliance across your fleet. For consumer users, Chrome typically auto-updates; force a manual check if a system has not been restarted recently. No workarounds exist; patching is the only remediation.

Detection guidance

Monitor for exploitation signals including: abnormal child process spawning from Chrome, unexpected system calls from the browser process, and access to sensitive OS resources from a Chrome renderer context. Web application firewalls and endpoint detection and response (EDR) tools should flag attempts to deliver known sandbox-escape payloads. Network-level detection is limited since the vulnerability requires renderer compromise first; prioritize endpoint telemetry. Check browser logs for unexpected crashes or renderer terminations, which may indicate exploitation attempts.

Why prioritize this

Although this vulnerability does not appear on CISA's Known Exploited Vulnerabilities catalog, the combination of high CVSS severity, sandbox escape capability, and potential for chained exploitation warrants immediate prioritization. Sandbox escapes are foundational attack primitives that enable secondary exploitation of the OS. Any environment where Chrome processes untrusted content—essentially all deployments—should be considered at-risk. For security teams, this should be classified as urgent and tracked separately from lower-severity browser patches.

Risk score, explained

The CVSS 3.1 score of 8.3 (High) is justified by: (1) network attack vector—exploitation can be triggered remotely via a webpage; (2) high complexity required, reflecting the prerequisite renderer compromise; (3) user interaction required to visit the malicious page; (4) scope change—the impact extends beyond the renderer to system-level resources; and (5) high impact across confidentiality, integrity, and availability. The score appropriately reflects both the effort required to exploit and the severity of successful compromise.

Frequently asked questions