External risk intelligence

Google Chrome WebGL Out of Bounds Write Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87438

The vulnerability exists in the WebGL implementation of a widely used web browser. Web browsers are primary internet-facing applications, and processing crafted HTML pages from the internet is a standard, expected function, making this surface commonly reachable.

Out-of-bounds Write

Google Chrome

before 153.0.8010.36

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical vulnerability in Google Chrome on Android could allow an attacker to execute code outside the browser's security protections. This issue arises from an out-of-bounds write in the WebGL component, which can be triggered by a malicious HTML page. While further analysis is needed to confirm the specific impact and exploitability, the severity rating indicates a significant potential risk.

  • Web browser code execution flaw identified.
  • Widely used browser technology; potential reach.
  • Confirm relevance; understand potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could target users by sending them to a malicious webpage. This page would leverage a flaw in the browser's WebGL component, allowing the attacker to execute code beyond the browser's security boundaries.

  • Entry condition: Attacker must direct user to a malicious webpage.
  • Trigger point: User visits the crafted HTML page.
  • Resulting risk: Arbitrary code execution outside the sandbox.

Live Threat

Current exploitation, exposure, and threat context

A critical vulnerability in Chrome's WebGL component on Android could allow a remote attacker to execute arbitrary code. This could occur when a user visits a malicious HTML page, potentially impacting the device's security and data.

  • Arbitrary code execution.
  • Malicious HTML page visits.
  • Compromise of device security.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome's WebGL implementation on Android requires immediate attention from teams managing web browsers and user endpoints. The first practical step is to identify all Android devices running affected Chrome versions, confirm their exposure to untrusted web content, and determine their criticality to business operations. Once accountable owners are identified, a coordinated remediation plan, prioritizing high-risk assets, can be developed.

  • Browser and endpoint owners should act.
  • Verify Chrome version and reachability.
  • Plan risk-based remediation actions.

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 WebGL in Google Chrome?

WebGL is a JavaScript API used within the browser to render high-performance 2D and 3D graphics. It allows Chrome to interact with the device's graphics processing unit (GPU) to display complex visual content on websites without needing additional plugins. This component is integrated directly into the browser's engine.

What does the CVE-2026-87438 out-of-bounds write mean?

This is a memory corruption flaw categorized as CWE-787. It occurs when a program writes data past the end of an intended memory buffer. In this case, the WebGL component fails to properly validate the size of data, allowing an attacker to overwrite adjacent memory, which can lead to arbitrary code execution outside the browser's sandbox.

How is this vulnerability triggered?

The flaw is triggered when a user navigates to a specifically crafted HTML page designed to exploit the WebGL component. Simply having the browser installed is not enough to trigger the bug; the browser must actively process the malicious graphics instructions contained within the webpage. Standard, non-malicious web browsing does not trigger this issue.

Do I need to worry about this vulnerability?

Halo Surface Signal identifies this as a highly relevant issue because web browsers are inherently internet-facing applications. Since the browser regularly processes external, untrusted content from the web, devices running the affected version of Chrome on Android are exposed to this risk if a user visits a malicious site.

When should I update Google Chrome for Android?

You should prioritize updating Chrome as soon as a patch is available. Begin by auditing your fleet to identify all Android devices running versions prior to 153.0.8010.36. Focus your remediation efforts on devices that frequently access untrusted web content or are critical to your operations, ensuring those browsers are moved to the secure version immediately.

References