Sandbox escape via WebGL out-of-bounds write
Published Sep 9, 2026 · Updated Sep 10, 2026
Out-of-bounds write in Google Chrome for Android before 153.0.8010.36 allows remote attackers to execute code outside the sandbox. A crafted HTML page reaches WebGL and causes a write beyond an allocated memory boundary; Google has not disclosed the affected WebGL operation or buffer. Visiting attacker-controlled content is sufficient, and successful exploitation escapes the renderer sandbox rather than remaining confined to it.
Summary
What happened
Out-of-bounds write in Google Chrome for Android before 153.0.8010.36 allows remote attackers to execute code outside the sandbox. A crafted HTML page reaches WebGL and causes a write beyond an allocated memory boundary; Google has not disclosed the affected WebGL operation or buffer. Visiting attacker-controlled content is sufficient, and successful exploitation escapes the renderer sandbox rather than remaining confined to it.
The record
- CVE
- CVE-2026-87438
- Published
- Sep 9, 2026
- Updated
- Sep 10, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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.
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