Sandbox escape via GPU buffer overflow
Published Sep 1, 2026 · Updated Sep 3, 2026
Buffer overflow in Google Chrome's GPU component before 152.0.7977.75 on Windows allows remote attackers to execute code outside the sandbox. Google has not disclosed the specific GPU code locus or bounds-checking operation that mishandles attacker-controlled data. Exploitation requires a crafted HTML page and an already compromised renderer process, after which code executes beyond the renderer sandbox.
Summary
What happened
Buffer overflow in Google Chrome's GPU component before 152.0.7977.75 on Windows allows remote attackers to execute code outside the sandbox. Google has not disclosed the specific GPU code locus or bounds-checking operation that mishandles attacker-controlled data. Exploitation requires a crafted HTML page and an already compromised renderer process, after which code executes beyond the renderer sandbox.
The record
- CVE
- CVE-2026-84351
- Published
- Sep 1, 2026
- Updated
- Sep 3, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-121, T1211
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=152.0.7977.75 <152.0.7977.75
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo