External risk intelligence

Chrome for Android GPU Use After Free Sandbox Escape

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-15900

This vulnerability exists within the client-side GPU processing of a web browser on Android. It requires a user to navigate to a crafted HTML page, making it a client-side interaction rather than a service-side or internet-facing network infrastructure exposure.

Use After Free

Google Chrome

before 150.0.7871.128

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 has been identified in Google Chrome on Android, stemming from a use-after-free flaw within the GPU component. While requiring user interaction via a malicious webpage, this issue could potentially allow for a sandbox escape, a significant security concern. The main concern at this stage is confirming relevance and exposure.

  • Browser flaw may allow deeper system access.
  • Protects users from malicious web content.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious web page, which then interacts with a use-after-free vulnerability in Chrome's Android GPU component. This interaction could allow the attacker to break out of the browser's sandbox, potentially leading to further compromise of the device.

  • Requires a user to visit a crafted page.
  • Triggered by GPU component interaction.
  • Risk of sandbox escape.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability, when supported by the advisory, could allow a remote attacker to escape the browser's sandbox. This occurs through a crafted HTML page, potentially impacting the security of the Android device by enabling malicious code to run outside of its intended, isolated environment.

  • Sensitive system data could be exposed.
  • Via a malicious HTML page.
  • Sandbox escape may lead to broader compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Chrome for Android's GPU component requires immediate attention from teams managing Android device fleets and user-facing applications. The first practical step is to identify all Android devices running affected Chrome versions, confirm if they access potentially malicious web content, and then coordinate remediation with either the mobile device management (MDM) team or application owners responsible for managing browser configurations and user experience.

  • Identify affected Android devices.
  • Verify user exposure to crafted web pages.
  • Plan and execute browser updates.

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 on Android?

It is a mobile web browser that allows users to navigate the internet. It uses a GPU component to accelerate the rendering of complex graphics and visual elements found on websites, which is the specific part of the software involved in this vulnerability.

What does use-after-free mean for CVE-2026-15900?

This is a memory management error classified as CWE-416. It happens when a program continues to use a memory address after it has been cleared or deleted. In this case, an attacker can manipulate this flaw to cause unpredictable behavior or gain unauthorized control over the browser's execution environment.

How is this vulnerability triggered?

The flaw is triggered when a user visits a specially crafted HTML page designed to interact with the browser's GPU processing. Simply having the browser installed is not enough; the attack requires a user to actively load and interact with the malicious content.

Is this a risk to my internet-facing servers?

According to Halo Surface Signal, this is very unlikely. The vulnerability resides in client-side GPU processing on Android devices rather than server-side infrastructure. It is a user-interaction issue, not a direct network-facing service exposure.

How do I address this Chrome vulnerability?

The most effective response is to update Chrome on all affected Android devices to the latest secure version. Teams should inventory their managed mobile devices to identify those running older versions and coordinate the deployment of browser updates through mobile device management platforms.

References