Executive brief
A security vulnerability exists in the Google Chrome web browser on Windows. If a user visits a specially crafted malicious website, an attacker who has already gained partial control of the browser's rendering process could bypass security restrictions (the 'sandbox') that normally isolate the browser from the rest of the computer. This could allow the attacker to gain broader access to the underlying operating system, potentially leading to data theft or unauthorized software installation.
Technical details
A use-after-free (UAF) vulnerability exists in the 'Core' component of Google Chrome for Windows. The flaw is triggered when the browser incorrectly manages memory during the processing of HTML content. To exploit this, an attacker must first compromise the renderer process (typically via a separate vulnerability). Once the renderer is compromised, the attacker can use a crafted HTML page to trigger the UAF condition and escape the Chrome sandbox, achieving execution in the context of the browser process or the underlying OS. This issue is resolved in 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