External risk intelligence

Google Chrome for Android WebGL Use-After-Free Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87488

This vulnerability exists in the WebGL implementation of a web browser client. Exploitation requires a user to navigate to a specifically crafted webpage. As a client-side component, it is not a network-exposed service, gateway, or internet-facing infrastructure component, making it very unlikely to be reachable as a public-facing attack surface.

Use After Free

Google Chrome

before 153.0.8010.36

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability exists in the WebGL component of Google Chrome on Android, potentially allowing attackers to execute malicious code. This could impact user devices if they visit a compromised webpage.

  • Browser code flaw can be exploited remotely.
  • Affects user devices via web browsing.
  • Confirm relevance and user exposure.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage, which then triggers a flaw in the browser's graphics processing. This could allow the attacker to run their own code on the user's device, potentially outside of the browser's security boundaries.

  • Requires user to visit a malicious page.
  • Triggered by WebGL rendering.
  • Remote code execution possible.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's WebGL component on Android could allow an attacker to execute arbitrary code outside the browser's sandbox when a user visits a malicious HTML page. This could compromise the integrity of the user's device.

  • Arbitrary code execution.
  • Via crafted HTML page.
  • Device compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome's WebGL component on Android could allow remote code execution via a crafted HTML page. The first practical step is to identify affected Android devices, confirm exposure, and assign ownership for remediation, likely involving application owners and potentially a vendor management team if custom integrations are involved.

  • Own by App or Device Owners.
  • Verify WebGL reachability and criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Google Chrome for Android and how does it use WebGL?

Google Chrome for Android is a web browser used to access internet content on mobile devices. It includes WebGL, a JavaScript API that enables the browser to render high-performance 2D and 3D graphics directly within the browser window without needing additional plugins. This feature allows websites to display complex visual effects, interactive animations, and graphics-intensive games.

What does a use-after-free weakness mean in CVE-2026-87488?

A use-after-free is a memory management error. It occurs when a program continues to use a pointer to a memory location after that memory has been cleared or freed. In the context of this CVE, it indicates a flaw in how the browser's WebGL component handles memory. An attacker can manipulate this state to trick the browser into executing arbitrary code by accessing that freed memory location.

How is this WebGL vulnerability triggered?

The vulnerability is triggered when a user navigates to a specifically crafted HTML page containing malicious WebGL instructions. Simply having the browser installed does not trigger the flaw; the user must actively visit the compromised webpage. It is not triggered by standard web browsing on reputable, secure sites that do not contain these specific malicious graphics commands.

Is my device at risk based on Halo Surface Signal?

Halo Surface Signal identifies this as very unlikely to be reachable as a public-facing attack surface. Because the vulnerability exists within a client-side browser component rather than an internet-facing server, gateway, or infrastructure service, it does not present a traditional network-based exposure. Risk is limited to scenarios where a user interacts with a malicious, specifically crafted website.

Do I need to take action to secure my devices?

Yes. Since this vulnerability affects the browser, you should verify the version of Google Chrome on your Android devices to confirm if they are running a vulnerable build. The primary response involves identifying affected devices and ensuring they are updated to the latest available version provided by the vendor, which includes the security fixes necessary to address this memory handling flaw.

References