CVE-2026-9974: Chrome GPU Out-of-Bounds Write Sandbox Escape (CVSS 8.3)

Technical summary

This vulnerability is classified as an out-of-bounds write (CWE-787) affecting the GPU subsystem in Chromium-based Chrome. The flaw exists in versions prior to 148.0.7778.216. The attack chain requires two prerequisites: first, a compromise of the renderer process (the sandboxed component that executes web content), and second, user interaction to load a crafted HTML page. Successfully exploiting the out-of-bounds write can corrupt GPU memory structures, potentially enabling a sandbox escape that elevates attacker capabilities from renderer-level to system-level access. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects network attack feasibility, high attack complexity due to the need for prior renderer compromise, required user interaction, and scope change to resources outside the renderer sandbox.

Business impact

A successful exploit chain could allow an attacker who has already compromised a user's Chrome renderer process to break out of the browser sandbox and gain system-level code execution. This transforms a browser-based attack into full device compromise, potentially enabling data theft, credential harvesting, malware installation, or lateral movement to internal networks. Organizations where employees browse untrusted websites remain at risk despite Chrome's multi-layered defenses. The attack requires user interaction but no special privileges, making it practical for targeted campaigns against high-value targets.

Affected systems

Google Chrome versions prior to 148.0.7778.216 are vulnerable on Windows, macOS, and Linux systems. The vulnerability affects the cross-platform GPU rendering code, so all operating systems running affected Chrome versions are at risk. The Linux kernel itself is not the source of the vulnerability but is listed as an affected platform where Chrome runs. Organizations should inventory Chrome deployments across all operating systems and prioritize updates.

Exploitability

Exploitation is moderately difficult but not theoretical. An attacker must first compromise the Chrome renderer process through a separate vulnerability or social engineering, then serve a specially crafted HTML page to trigger the GPU out-of-bounds write. The high attack complexity (reflected in the CVSS vector) and requirement for prior renderer compromise limit opportunistic exploitation, but targeted attacks against known renderer vulnerabilities followed by this GPU escape are plausible. Chromium security severity is rated High, indicating Google considers this a priority fix. The vulnerability is not currently listed on the CISA KEV catalog, suggesting no public active exploitation has been reported at publication time.

Remediation

Update Google Chrome to version 148.0.7778.216 or later immediately. Chrome's automatic update mechanism should deploy the fix, but users should verify their version in Settings > About Chrome and manually trigger updates if needed. Organizations managing Chrome fleet-wide should use endpoint management tools to enforce the update. No workarounds bypass the sandbox escape risk; updating is the only mitigation. Users on older operating systems unable to run newer Chrome versions should consider additional security controls such as application whitelisting or browser isolation solutions.

Patch guidance

Google released the fix in Chrome 148.0.7778.216 on the publication date of this CVE. Verify your Chrome version by navigating to chrome://settings/help, which will also automatically check for and install updates. For enterprise deployments, confirm patch status through your mobile device management (MDM) or endpoint management platform. If you use Chromium or Chromium-based browsers (Edge, Brave, Opera, etc.), check those vendors' advisories for corresponding patch availability, as they may lag behind Chrome's release schedule. No manual patch application is required for standard Chrome installations.

Detection guidance

Monitor for anomalous GPU process activity and unexpected system calls originating from Chrome's GPU utility process. Detect exploitation through Chrome crash logs and system error reports indicating GPU memory corruption. Organization-wide, look for suspicious Chrome renderer crashes followed by system-level process creation or registry modifications, which may indicate a successful sandbox escape. Endpoint detection and response (EDR) tools should flag GPU process elevation attempts or unusual inter-process communication between Chrome components and system services. Log and alert on users visiting untrusted websites during periods when you know their Chrome version is unpatched.

Why prioritize this

Prioritize this patch within 1–2 weeks. While exploitability requires prior renderer compromise, successful exploitation results in complete system compromise. The sandbox escape amplifies the impact of other Chrome vulnerabilities, making this a high-value fix for attackers in targeted campaigns. Chromium's High severity rating and the scope change to system-level resources justify urgent but not emergency treatment. Organizations with high-risk user populations (security researchers, journalists, activists) should patch within days. Standard business users should patch within 2 weeks.

Risk score, explained

The CVSS 8.3 (HIGH) score reflects a network-accessible vulnerability with high impact across confidentiality, integrity, and availability, but requiring high attack complexity due to the need for prior renderer compromise and user interaction. The scope change (S:C) acknowledges that successful exploitation impacts resources beyond the renderer sandbox. This score appropriately represents a serious but not critical vulnerability—serious because it enables system-level access, but not critical because it requires chaining with another vulnerability and user action.

Frequently asked questions