Process-memory disclosure via uninitialized GPU data
Published Jun 24, 2026 · Updated Jun 24, 2026
Uninitialized memory use in Google Chrome on Android before 149.0.7827.197 allows remote attackers to read process memory via crafted HTML. The public record identifies the GPU component but does not disclose which code path consumes uninitialized storage or how the crafted page exposes it. A user must open the crafted page on an affected Android device; the documented consequence is process-memory disclosure, with no integrity or availability impact.
Summary
What happened
Uninitialized memory use in Google Chrome on Android before 149.0.7827.197 allows remote attackers to read process memory via crafted HTML. The public record identifies the GPU component but does not disclose which code path consumes uninitialized storage or how the crafted page exposes it. A user must open the crafted page on an affected Android device; the documented consequence is process-memory disclosure, with no integrity or availability impact.
The record
- CVE
- CVE-2026-13030
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-457, T1189
- 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