Process-memory disclosure via uninitialized GPU data
Published Jun 24, 2026 · Updated Jun 24, 2026
Uninitialized GPU memory use in Google Chrome before 149.0.7827.197 allows remote attackers to read process memory via crafted HTML. Google has not published the GPU code path or operation that consumes uninitialized data because the linked issue remains restricted. Exploitation requires prior compromise of a renderer process and exposes potentially sensitive process-memory contents without reported modification or service interruption.
Summary
What happened
Uninitialized GPU memory use in Google Chrome before 149.0.7827.197 allows remote attackers to read process memory via crafted HTML. Google has not published the GPU code path or operation that consumes uninitialized data because the linked issue remains restricted. Exploitation requires prior compromise of a renderer process and exposes potentially sensitive process-memory contents without reported modification or service interruption.
The record
- CVE
- CVE-2026-13023
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-457, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=149.0.7827.197 <149.0.7827.197
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