CVE-2026-9876
A critical flaw in Chrome’s WebGL implementation on Android lets a remote attacker use a specially crafted web page to escape the browser sandbox. The bug is a use‑after‑free that can be triggered over the network. It affects Chrome versions before 148.0.7778.216 on Android devices.
No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.
Who is affected
Google Chrome on Android devices running versions earlier than 148.0.7778.216.
Real-world impact
An attacker could run code outside the browser sandbox, potentially accessing the device’s file system, network, or other apps.
Why this severity
The CVSS score of 9.6 reflects that the flaw can be exploited remotely (AV:N), requires minimal effort (AC:L), no special privileges (PR:N), but needs user interaction with a web page (UI:R). The vulnerability changes the security scope (S:C) and can compromise confidentiality, integrity, and availability (C:H/I:H/A:H).
What to do about it
No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.
No fix documented in sources
Timeline
- May 28, 2026 · May 28, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 21, 2026 · 14d agoAdvisory updatedThe NVD record was last revised.
How it’s attacked
References & advisories
- chromereleases.googleblog.com/2026/05/stable-channel-upda…release notes
- issues.chromium.org/issues/493747593permissions required