CVE-2026-84351: Buffer overflow in GPU
Buffer overflow in GPU in Google Chrome on on Windows prior to 152.0.7977.75 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Other sources
Chromium: CVE-2026-84351 Buffer overflow in GPU
— Microsoft
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 152.0.7977.75 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 152.0.4191.62 - Upgrade
Upgrade
Google Chrome (Windows)to a version that resolves this vulnerability.Fixed in 152.0.7977.75
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-84353
- CVE-2026-84352
- CVE-2026-84354
- CVE-2026-84359
- CVE-2026-84357
- CVE-2026-84324
- CVE-2026-84349
- CVE-2026-84326
- CVE-2026-84333
- CVE-2026-84325
- CVE-2026-84328
- CVE-2026-84347
- CVE-2026-84323
- CVE-2026-84355
- CVE-2026-84358
- CVE-2026-84332
- CVE-2026-84330
- CVE-2026-84334
- CVE-2026-84348
- CVE-2026-84335
- CVE-2026-84327
- CVE-2026-84329
- CVE-2026-84356
- CVE-2026-84350
- CVE-2026-84331
Frequently Asked Questions
Which systems are affected?
The issue affects Google Chrome on Windows before version 152.0.7977.75. The provided information does not identify impact on other operating systems.
What does an attacker need to exploit this vulnerability?
The attacker must first compromise the Chrome renderer process. They can then use a crafted HTML page to trigger the GPU buffer overflow and execute code outside Chrome's sandbox.
Are users exposed simply by visiting a malicious page?
Not based on the available information. A crafted HTML page is part of the exploit chain, but the renderer process must already be compromised.
How can I determine whether an installation is affected?
Check the Chrome version on Windows. Versions earlier than 152.0.7977.75 are affected according to the provided information.