CVE-2026-9876: Use after free in WebGL in Google Chrome on Android prior to 148
Use after free in WebGL in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
HarborGuard Analysis
HarborGuard analysisSynopsis
Use-after-free in the WebGL component of Google Chrome on Android (versions prior to 148.0.7778.216) allows a remote attacker to exploit freed memory through a crafted HTML page. The vulnerability is reachable over the network with no authentication required, but does need the victim to visit a malicious page; the CVSS scope is changed, meaning a successful exploit can break out of the Chrome sandbox entirely. A successful attack gives the attacker full read, write, and availability impact on the affected host, including the ability to escape the browser sandbox. A patched-image rebuild at 148.0.7778.216 is available on HarborGuard for environments running an affected version.
HarborGuard Coverage
Detection of CVE-2026-9876 is available across every HarborGuard environment; the CVE is ingested from upstream feeds within minutes of publication and matched against container images in customer registries and CI/CD pipelines, including custom-built Android or Chrome-based images. Any image shipping a Chrome version below 148.0.7778.216 on an Android base is flagged automatically.
AvailableHarborGuard scores this vulnerability at CVSS 9.6 (Critical) using the published v3.1 vector and can weight that score against each customer organization's per-environment compliance policy to determine urgency. Routed findings land in the appropriate team inbox based on each customer's configured ownership rules, so the right engineers see the alert without manual triage overhead.
AvailableA patched-image rebuild at Chrome 148.0.7778.216 becomes available in HarborGuard the moment the fix version is resolvable in the relevant package feeds. For customers who opt into auto-remediation, HarborGuard performs a rebuild, runs a regression test suite, and opens a pull request against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker must reach the victim's browser over the network by serving a crafted HTML page from a remote host.
- AuthenticationNot required
No account or credential of any kind is required; any unauthenticated remote party can deliver the malicious page.
- Victim interactionRequired
The victim must navigate to or be redirected to the attacker-controlled HTML page, making this a social-engineering or drive-by scenario.
- Attack complexityDetail
Attack complexity is Low, meaning the exploit is reliable and requires no special race conditions, memory-layout guessing, or other environmental preconditions.
Blast Radius
- Attacker reads arbitrary memory within the Chrome process, including stored session tokens, cookies, and cached credentials.
- Attacker writes to process memory, enabling code execution inside the renderer and a full sandbox escape to the underlying Android OS.
- With sandbox escape achieved, the attacker gains the ability to read, modify, or delete files and data accessible to the Chrome process on the device.
- Service availability is fully compromised; the attacker can crash the browser process or execute persistent code on the host.
How HarborGuard Handles This
Available on HarborGuard: detection for CVE-2026-9876 is active across all connected registries and pipelines, matching images against the affected Chrome version range on Android bases. For environments where a fix is available (Chrome 148.0.7778.216), a patched-image rebuild is ready to trigger. Customers with auto-remediation enabled receive a rebuilt image, a regression-test run, and a PR opened against affected workloads; for Critical-severity issues, the median time from CVE publication to merged patch PR in auto-remediation environments is around 90 minutes. Where compliance policy requires manual approval, the rebuilt image and test results are staged and waiting for engineer sign-off. Customers who cannot immediately rebuild should consider network-policy controls that restrict access to untrusted web content from affected Android Chrome deployments as a compensating control until the patched image is deployed.
Metrics
- CVSS v3.1
- 9.6
- Severity
- CRITICAL
- Fixed in
- 148.0.7778.216
- Affected Products
- 1
Fix available
- Google / Chrome< 148.0.7778.216 (from 148.0.7778.216)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H