External risk intelligence

Chrome for Android Use-After-Free Vulnerability Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-110165

The vulnerability exists within the Google Chrome browser on Android. Exploitation requires a user to navigate to a crafted HTML page, making it a client-side interaction rather than a service or infrastructure component that is typically exposed as a public-facing internet service or gateway.

Use After Free

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 for Android could allow attackers to execute code outside the browser's security boundaries if a user visits a specially crafted web page. While exploitation requires user interaction, the potential for code execution warrants attention to understand its relevance to our environment.

  • A flaw in Chrome for Android allows remote code execution.
  • This could impact user security if a malicious site is visited.
  • Confirm relevance and assess potential exposure within the organization.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious website, which then triggers a flaw in Chrome's Core. This flaw could allow them to run their own code, potentially gaining unauthorized access to the device.

  • Requires user interaction via a web page.
  • Triggered by a use-after-free vulnerability.
  • Risk of code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Google Chrome on Android, prior to version 155.0.8059.79, could allow a remote attacker to execute arbitrary code outside the sandbox by tricking a user into visiting a malicious HTML page. This means an attacker could potentially take control of the affected device's actions.

  • Device code execution.
  • Visiting a malicious HTML page.
  • Arbitrary code execution outside sandbox.

Operational Fix

Recommended remediation, mitigation, and detection steps

The real-world impact of this use-after-free vulnerability in Chrome on Android primarily affects end-users and requires interaction through a malicious HTML page. While the vulnerability is critical, its exploitation often relies on user behavior, meaning the immediate focus for technical leaders and security teams should be on understanding user exposure and coordinating with vendor communications. First steps involve identifying which user groups or devices may be affected, confirming if the exploit is practically achievable in your environment, and then planning a targeted update strategy based on risk.

  • Identify accountable application or device owners.
  • Verify user exposure to malicious websites.
  • Coordinate browser updates with 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 for Android?

Google Chrome for Android is a widely used mobile web browser that allows users to navigate the internet, render complex web pages, and run web-based applications on Android devices. It serves as the primary interface for web interactions, managing security through a sandbox environment designed to isolate web content from the underlying operating system.

What does this use-after-free vulnerability mean in CVE-2026-110165?

This vulnerability is a memory management flaw categorized as a Use After Free (CWE-416). It occurs when the browser continues to use a memory location after that memory has been cleared or freed. Because the program incorrectly attempts to access this stale data, an attacker can manipulate the state of the browser to execute unauthorized code outside of its intended security boundaries.

How does an attacker trigger this Chrome vulnerability?

The vulnerability is triggered when a user navigates to a malicious or specially crafted HTML page. It does not trigger automatically; the browser must process the harmful web content for the flaw to manifest. Simply having the browser installed or running in the background without user interaction with the crafted site does not initiate the exploit.

Is my organization at risk from this Chrome for Android issue?

Halo Surface Signal indicates that this is a client-side vulnerability, making it less likely to impact your primary public-facing infrastructure. Because it requires a user to actively visit a malicious site on an affected mobile device, the risk is tied to individual user behavior rather than your server-side network security or internal service configuration.

How should I respond to CVE-2026-110165?

The most effective step is to ensure that mobile devices are updated to Chrome version 155.0.8059.79 or later, which contains the fix. Prioritize identifying which users or departments rely on these mobile devices and coordinate a timely update strategy to bring them onto the supported, secure version of the browser.

References