CVE-2026-102301: Out of bounds write in GPU
Out of bounds write in GPU in Google Chrome prior to 154.0.8037.92 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
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 154.0.8037.92
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-102331
- CVE-2026-102317
- CVE-2026-102312
- CVE-2026-102313
- CVE-2026-102299
- CVE-2026-102306
- CVE-2026-102307
- CVE-2026-102323
- CVE-2026-102303
- CVE-2026-102311
- CVE-2026-102300
- CVE-2026-102326
- CVE-2026-102316
- CVE-2026-102304
- CVE-2026-102328
- CVE-2026-102309
- CVE-2026-102325
- CVE-2026-102308
- CVE-2026-102319
- CVE-2026-102324
- CVE-2026-102318
- CVE-2026-102329
- CVE-2026-102315
- CVE-2026-102302
- CVE-2026-102321
- CVE-2026-102320
- CVE-2026-102310
- CVE-2026-102327
- CVE-2026-102330
- CVE-2026-102314
- CVE-2026-102305
Frequently Asked Questions
What must an attacker achieve before this flaw can be used to escape the sandbox?
The attacker must first compromise the Chrome renderer process. The issue can then potentially allow arbitrary code execution outside the sandbox through a crafted HTML page.
Which Chrome installations are affected?
Google Chrome versions prior to 154.0.8037.92 are affected. Updating to 154.0.8037.92 or later addresses the affected version range described.
Is ordinary web browsing alone described as sufficient for exploitation?
No. The description specifically requires that the attacker has already compromised the renderer process; it does not state that visiting a crafted page alone is sufficient.