Sandboxed code execution via GPU use-after-free
Published May 20, 2026 · Updated May 20, 2026
GPU use-after-free in Google Chrome on Windows before 148.0.7778.179 allows remote attackers to run sandboxed code via crafted HTML. Google identifies the GPU component as the locus but has not disclosed the affected function, object, or operation on freed memory. Exploitation requires a Windows user to load an attacker-controlled page; the reported code execution remains inside Chrome's sandbox.
Summary
What happened
GPU use-after-free in Google Chrome on Windows before 148.0.7778.179 allows remote attackers to run sandboxed code via crafted HTML. Google identifies the GPU component as the locus but has not disclosed the affected function, object, or operation on freed memory. Exploitation requires a Windows user to load an attacker-controlled page; the reported code execution remains inside Chrome's sandbox.
The record
- CVE
- CVE-2026-9112
- Published
- May 20, 2026
- Updated
- May 20, 2026
- Vendor
- The fscrypt Project
- Product
- Chrome
- Classifications
- CWE-416, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 20, 2026CVE publishedPublication date reported by the CVE source.
- May 20, 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 version<148.0.7778.179
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us