External risk intelligence

Chrome for Android Use After Free in Navigation Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-121241

This vulnerability affects a client-side web browser. While it requires a user to interact with malicious web content, the browser itself is a client application, not a public-facing service, gateway, or internet-accessible appliance. Therefore, it does not fit the criteria of an externally reachable attack surface in common server-side or infrastructure deployments.

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 use-after-free vulnerability in Chrome's navigation feature on Android could allow a remote attacker to execute arbitrary code outside the sandbox by tricking a user into visiting a malicious web page.

  • A browser flaw may allow malicious code execution.
  • It impacts a widely used application on mobile devices.
  • Confirm relevance and exposure for affected users.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious web page. This page would contain specially crafted code designed to exploit a flaw in how Chrome on Android handles navigation. If successful, this could allow the attacker to execute their own code on the user's device, potentially impacting their data and privacy.

  • Requires user interaction with a malicious page.
  • Triggered by a use-after-free vulnerability.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's navigation on Android could allow a remote attacker to execute arbitrary code outside the browser's sandbox by tricking a user into visiting a malicious HTML page. This exploit could lead to a compromise of the user's device, though the specific data at risk depends on the sandbox's effectiveness and the attacker's capabilities.

  • User's device data at risk.
  • Visiting a malicious webpage.
  • Potential arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Google Chrome on Android, specifically impacting the Navigation component. Real-world ownership likely falls to the Android application support team or a dedicated Chrome management team if one exists, with potential involvement from the security team for exposure assessment. The first practical move is to confirm the presence of the affected Chrome version across the Android fleet, assess user exposure and criticality, and then coordinate with the vendor for updates.

  • Ownership: Android application support or Chrome management.
  • Verify: Affected Chrome version presence and user exposure.
  • Action: Plan and deploy vendor 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?

Google Chrome for Android is the mobile version of Google's web browser, used for accessing websites and web applications on Android devices. It includes a navigation component responsible for handling the movement between different web pages and managing browser history and state.

What does CWE-416 mean for CVE-2026-121241?

CVE-2026-121241 involves a 'Use After Free' weakness (CWE-416). This occurs when the browser continues to reference a piece of computer memory after it has already been cleared or released. An attacker can manipulate this flaw to replace the old data with their own malicious instructions, potentially gaining unauthorized control over the browser's operations.

How is this vulnerability triggered?

This flaw is triggered when a user navigates to a specifically crafted malicious HTML page that forces the browser to mishandle memory during the navigation process. Simply having the browser installed or running it on a secure, known website will not trigger the vulnerability; it requires active interaction with compromised content.

Does this impact my infrastructure according to Halo Surface Signal?

Halo Surface Signal indicates this is unlikely to affect typical server-side infrastructure. Because Chrome is a client-side application running on individual mobile devices rather than a public-facing network service or gateway, the attack surface is focused on the end-user's device rather than corporate network boundaries.

What should I do if I manage Android devices?

Begin by identifying which Android devices in your fleet are running Chrome versions earlier than 157.0.8103.38. Once identified, prioritize coordinating with your device management or application support teams to deploy the latest vendor updates, which contain the necessary code fixes to address this navigation memory flaw.

References