Executive brief
A memory management vulnerability in Google Chrome's graphics processing component could allow an attacker to bypass security boundaries. If a user visits a specially crafted website, an attacker who has already compromised the browser's content rendering process could escape the 'sandbox' to gain broader access to the underlying system. This could lead to unauthorized access to user data or the execution of malicious code outside the browser's restricted environment.
Technical details
A use-after-free (UAF) vulnerability exists in the GPU component of Google Chrome. The flaw is triggered when the browser incorrectly manages memory pointers after an object has been deleted. An attacker who has already achieved code execution within a compromised renderer process can exploit this vulnerability by enticing a user to visit a malicious HTML page. Successful exploitation allows the attacker to perform a sandbox escape, moving from the restricted renderer process to the more privileged GPU process or the host operating system. The issue is resolved in Chrome version 148.0.7778.216 and later.
Affected products
- Google Chrome Prior to 148.0.7778.216
Timeline
- 2026-05-27: patched: Stable channel update released for desktop
- 2026-05-28: disclosed: CVE published to NVD