CVE-2026-12023: Chrome GPU Use-After-Free Sandbox Escape on macOS

Technical summary

CVE-2026-12023 is a use-after-free vulnerability (CWE-416) in Chrome's GPU subsystem on macOS prior to version 149.0.7827.115. The flaw occurs when GPU memory is freed but references to it remain accessible, allowing use of stale pointers. An attacker with control of the renderer process can trigger this condition via crafted HTML, leading to out-of-bounds memory access. The vulnerability crosses sandbox boundaries (S:C in CVSS), meaning successful exploitation grants code execution in the browser process context rather than remaining confined to the renderer sandbox.

Business impact

A successful exploitation chain—initial renderer compromise followed by sandbox escape—grants an attacker the ability to run code with Chrome's full privileges on macOS. This enables theft of sensitive data, installation of malware, lateral movement to other processes, and persistent compromise of the user's system. For organizations with users on macOS, this represents a high-confidence path from web-based attack to system-level compromise.

Affected systems

Google Chrome versions prior to 149.0.7827.115 running on macOS are vulnerable. The vulnerability does not affect Windows or Linux Chrome builds, nor earlier or concurrent versions of other browsers. Organizations with macOS endpoints using older Chrome versions face direct exposure.

Exploitability

Exploitation requires two preconditions: (1) the renderer process must already be compromised (e.g., via a separate browser vulnerability or malicious website), and (2) the user must interact with a page containing the malicious HTML. The CVSS vector reflects high complexity (AC:H) due to these dependencies, but once those conditions align, sandbox escape is reliable. The attack does not require user privileges beyond normal browser interaction.

Remediation

Update Google Chrome on all macOS systems to version 149.0.7827.115 or later. Verify the update via Chrome's Settings > About Google Chrome, which will display the current version and trigger automatic updates if available. No workarounds exist for this GPU-level issue; patching is mandatory.

Patch guidance

Chrome updates deploy automatically on most systems, but administrators should verify completion across macOS device fleet. Confirm that no instances remain below 149.0.7827.115. If auto-updates are disabled in your environment, manually trigger updates through Chrome's settings or via Enterprise policy management tools (Chrome Enterprise users should consult their deployment console). Test patched versions in a limited rollout before full deployment if your workflow requires validation.

Detection guidance

Monitor Chrome process activity for GPU-related crashes or unexpected process termination, which may indicate exploitation attempts. Examine browser logs and crash reports for patterns involving GPU memory errors. Endpoint detection and response (EDR) tools should flag suspicious process spawning from Chrome's main process, particularly execution of shell commands or system utilities. Review web proxy or network logs for requests to sites known to host Chrome exploits or watering-hole attacks, though this is a reactive measure.

Why prioritize this

This vulnerability combines high severity (CVSS 8.3, confidentiality, integrity, and availability impact) with a realistic but non-trivial attack chain. It is not currently in the CISA KEV catalog, suggesting active in-the-wild exploitation has not been widely reported, but the GPU sandbox-escape vector is valuable enough for targeted attacks. Prioritize patching based on exposure: macOS endpoints with older Chrome versions in high-value roles (executives, developers, researchers) should be prioritized first, followed by broad fleet coverage.

Risk score, explained

The CVSS 8.3 score reflects the combination of network-based attack vector, high complexity due to prerequisite renderer compromise, required user interaction, and cross-sandbox impact (C, I, A all set to High). The score appropriately captures the severity of a sandbox escape, which is one of the most critical vulnerability classes in browser security. The absence of KEV listing indicates this is not yet weaponized at scale, keeping it from the highest tier, but organizations should not delay patching.

Frequently asked questions