Sandbox memory disclosure via uninitialized GPU resource
Published Sep 9, 2026 · Updated Sep 9, 2026
Uninitialized GPU resources in Google Chrome for Android before 153.0.8010.36 allow remote attackers to read memory outside the sandbox. Google identifies the GPU component but has not published the specific allocation, initialization path, or operation that exposes stale memory. Exploitation requires a crafted HTML page and prior compromise of the renderer process; the demonstrated consequence is out-of-sandbox memory disclosure.
Summary
What happened
Uninitialized GPU resources in Google Chrome for Android before 153.0.8010.36 allow remote attackers to read memory outside the sandbox. Google identifies the GPU component but has not published the specific allocation, initialization path, or operation that exposes stale memory. Exploitation requires a crafted HTML page and prior compromise of the renderer process; the demonstrated consequence is out-of-sandbox memory disclosure.
The record
- CVE
- CVE-2026-87576
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-908
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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=153.0.8010.36 <153.0.8010.36
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Weakness, pattern, technique
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