External risk intelligence

Chrome for Android GPU Out of Bounds Write Sandbox Escape

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-10892

This vulnerability exists within the GPU component of the Google Chrome browser on Android. Successful exploitation requires a user to navigate to a crafted HTML page, making it a client-side browser issue rather than a service or appliance exposed to the internet by design.

Out-of-bounds Write

Google Chrome

before 149.0.7827.53

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 in Google Chrome on Android could allow a remote attacker to bypass security protections through a malicious webpage, potentially impacting user data and system integrity. The primary concern is confirming relevance and exposure to our Android user base.

  • Browser flaw could bypass security.
  • Matters due to potential system access.
  • Verify Android Chrome exposure.

Attack Path

How an attacker could exploit the issue

An attacker can trick a user into visiting a malicious web page, which then triggers a flaw in Chrome's GPU component on Android. This could allow the attacker to break out of the browser's sandbox, potentially leading to broader system compromise.

  • No specific user privileges needed.
  • Triggered by visiting a crafted web page.
  • Risk of sandbox escape and system compromise.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could potentially escape the sandbox in Chrome on Android by directing a user to a malicious HTML page. This could affect the integrity of the user's device and expose sensitive information when supported by the advisory.

  • Sensitive user data.
  • Malicious HTML page.
  • Sandbox escape and data compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability in Google Chrome on Android requires immediate attention from teams responsible for mobile application security and endpoint management. The first step is to identify all Android devices running Chrome, confirm their exposure to malicious websites, and determine business criticality. Once ownership is established, a remediation plan can be developed.

  • Mobile application owners must investigate Chrome usage.
  • Verify Chrome browser reachability and business criticality.
  • Coordinate vendor updates and user communication.

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?

Google Chrome on Android is the mobile version of the widely used web browser, designed to render websites and execute complex web applications. It relies on the device's GPU to process graphics and video acceleration efficiently. This vulnerability specifically impacts the browser's GPU rendering engine, a core component responsible for handling visual content, which is a common target for complex security research.

What does an out-of-bounds write mean for CVE-2026-10892?

An out-of-bounds write (CWE-787) occurs when software writes data past the end of an allocated memory buffer. In this case, the GPU component fails to properly validate the size of data before writing it. This memory corruption can allow an attacker to overwrite adjacent data or code, potentially gaining control over the program's execution flow to escape the browser's security sandbox.

How is this Chrome vulnerability triggered?

An attacker must trick a user into navigating to a specifically crafted HTML page designed to exploit the GPU memory flaw. Simply having the browser installed or running in the background does not trigger the bug. If a user does not visit a malicious webpage, the vulnerable code path remains dormant, meaning standard, safe web browsing does not initiate the exploit.

Do I need to worry if Chrome is only used internally?

According to Halo Surface Signal, this is a client-side browser issue rather than a service or appliance exposed to the internet by design. While internal web apps are used, the risk is tied to the user visiting a crafted page, not the server's reachability. Organizations should prioritize devices where users frequently visit untrusted internet sites, as those present the highest risk of encountering a malicious trigger.

What are the first steps to address this CVE?

Your priority is to ensure all Android devices are running Chrome version 149.0.7827.53 or later. Begin by identifying managed mobile assets where Chrome is installed and verify their current software version. Once identified, ensure these devices receive the official vendor update, which resolves the memory handling flaw in the GPU component and mitigates the risk of sandbox escape.

References