Sandbox escape via raced WebGL element-array reads
Published May 28, 2026 · Updated May 28, 2026
Insufficient WebGL input validation in Google Chrome before 148.0.7778.216 allows remote attackers to escape the browser sandbox after renderer compromise. The WebGL element-array path reads shared-memory data more than once, allowing the data to change between validation and GPU upload. Exploitation requires a crafted page and prior renderer compromise; the resulting race crosses the renderer sandbox boundary.
Summary
What happened
Insufficient WebGL input validation in Google Chrome before 148.0.7778.216 allows remote attackers to escape the browser sandbox after renderer compromise. The WebGL element-array path reads shared-memory data more than once, allowing the data to change between validation and GPU upload. Exploitation requires a crafted page and prior renderer compromise; the resulting race crosses the renderer sandbox boundary.
The record
- CVE
- CVE-2026-9880
- Published
- May 28, 2026
- Updated
- May 28, 2026
- Vendor
- The fscrypt Project
- Product
- Chrome
- Classifications
- CWE-20, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2026CVE publishedPublication date reported by the CVE source.
- May 28, 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.216
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