CVE-2026-9900: Chrome ANGLE Out-of-Bounds Write & Sandbox Escape Vulnerability

Technical summary

CVE-2026-9900 is an out-of-bounds write vulnerability (CWE-787) in the ANGLE graphics library used by Google Chrome. The defect exists in versions prior to 148.0.7778.216. An attacker with a compromised renderer process can craft an HTML page that triggers the out-of-bounds write, potentially achieving sandbox escape and code execution at the system level. The vulnerability has a CVSS 3.1 score of 8.3 (High), reflecting the requirement for a compromised renderer (limiting initial attack surface) but the severity of sandbox escape as an impact.

Business impact

This vulnerability presents a two-stage attack: first compromising the renderer (via a separate vulnerability or XSS-like vector), then leveraging CVE-2026-9900 to escape the sandbox and control the host system. Organizations running Chrome on systems with sensitive data face elevated risk if their users visit untrusted sites. For enterprise environments, this creates incentive for attackers to chain multiple exploits to gain full endpoint control. The sandbox escape aspect is particularly concerning because it neutralizes Chrome's primary defense mechanism.

Affected systems

Google Chrome versions prior to 148.0.7778.216 are affected across all platforms where Chrome runs (Windows, macOS, Linux, Android, ChromeOS). Organizations should verify their deployed Chrome version and confirm whether auto-update has delivered the patch. This includes both user-installed Chrome and managed deployments.

Exploitability

Exploitation requires two conditions: (1) the renderer process must already be compromised by an attacker, and (2) the user must visit a page hosting a crafted HTML exploit. While the CVSS vector reflects these preconditions (AC:H, PR:N, UI:R), the sandbox escape itself is highly desirable for attackers. This is not a one-click remote code execution but a chained attack. The vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities catalog, though security researchers should assume proof-of-concept details will emerge as disclosure details circulate.

Remediation

Update Google Chrome to version 148.0.7778.216 or later. For managed environments, deploy this update through your standard patch management process and verify completion within 30 days. Organizations using Chrome OS should ensure auto-update is enabled and check admin consoles for deployment status. No workarounds exist; patching is the only mitigation.

Patch guidance

Apply Chrome version 148.0.7778.216 or later as soon as feasible. Most users on auto-update will receive this patch automatically; verify update completion by navigating to chrome://settings/help and confirming the version. For enterprise Chrome deployments, use Chrome Admin console or group policy to push the update to managed devices. Prioritize systems where users frequently visit untrusted or user-generated content (e.g., forums, social media).

Detection guidance

Monitor Chrome version compliance across your fleet to ensure no instances remain on pre-148.0.7778.216 builds. Logs of sandbox escapes are difficult to detect in real-time, but behavioral indicators include unexpected child process spawning from the Chrome process or unusual system-level activity correlated with browser activity. Endpoint Detection and Response (EDR) tools should be configured to alert on sandbox escape patterns. For network defense, monitor for beaconing or lateral movement immediately following suspicious browser activity.

Why prioritize this

Although this vulnerability requires a compromised renderer as a precondition, sandbox escape vulnerabilities are critical in browser security because they grant attackers unrestricted system access. This transforms a contained renderer compromise into a full system compromise. Organizations should treat this as high priority because: (1) it eliminates Chrome's last line of defense, (2) patches are available and easy to deploy, and (3) chained exploits targeting renderer + sandbox escape are a known attacker pattern. Prioritize systems handling sensitive workloads or accessed by high-value users.

Risk score, explained

The CVSS 3.1 score of 8.3 (High) reflects: high confidentiality/integrity/availability impact (sandbox escape grants full system control), network attack vector (HTML delivered over web), user interaction required (must visit page), and low attack complexity (only after renderer compromise). The score appropriately elevates what might initially seem like a limited-scope renderer issue to High because of the sandbox escape impact and widespread Chrome usage.

Frequently asked questions