External risk intelligence

Google Chrome Mobile Use After Free Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-121077

The vulnerability exists within the mobile web browser client. Exploitation requires a user to be socially engineered into visiting a crafted HTML page. As a client-side application, it is not a network-facing service, gateway, or internet-accessible infrastructure, and therefore does not have a public internet-facing attack surface in the context of common 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

This critical vulnerability in Google Chrome's mobile browser could allow a remote attacker to execute malicious code outside the browser's secure environment by tricking users into visiting a specially crafted webpage. While the immediate exposure appears low due to the need for user interaction and the fact it's a client-side application, its presence in a widely used browser warrants attention to confirm relevance and exposure within your organization.

  • A flaw lets attackers run code outside the browser.
  • It affects users who click malicious links.
  • Assess relevance and confirm exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious webpage. This page would exploit a use-after-free flaw in the browser's mobile application, potentially allowing the attacker to run their own code on the user's device, breaking out of the browser's security protections.

  • Requires user interaction.
  • Triggered by a malicious webpage.
  • Risk of code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome on mobile, when exploited through social engineering on a crafted HTML page, could allow an attacker to execute arbitrary code outside the sandbox. This could affect the integrity and confidentiality of data processed by the affected browser on the mobile device.

  • Arbitrary code execution on mobile devices.
  • Exploitation via a crafted HTML page.
  • Compromised device data and integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability resides within the mobile web browser client, and exploitation requires a user to visit a malicious HTML page via social engineering. Therefore, ownership likely falls to teams managing endpoint security and user-facing applications, with the first practical step being to confirm user exposure and the criticality of the affected application.

  • Own by endpoint security and app teams.
  • Verify user exposure and application criticality.
  • Plan user-centric remediation and 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 Mobile and why does it need security updates?

Google Chrome Mobile is a web browser application used on smartphones and tablets to access the internet. It relies on complex software components to render websites, manage memory, and protect user data. Regular updates are essential because they fix underlying code errors—like memory management flaws—that could otherwise be manipulated to bypass the browser's built-in security protections.

What does use-after-free mean in the context of CVE-2026-121077?

Use-after-free is a vulnerability class, specifically CWE-416, occurring when software continues to use a memory address after that memory has been cleared or released. In CVE-2026-121077, this flaw allows an attacker to manipulate the browser's memory. If successful, they can trick the software into running unauthorized code, effectively breaking the security boundaries designed to keep the browser isolated from the rest of your device.

How is this Chrome vulnerability triggered?

The trigger requires a multi-step process: an attacker must first use social engineering to convince a user to open a specifically crafted, malicious HTML webpage within the mobile browser. If the user does not visit this specific page, the vulnerability remains dormant. Simply having the browser installed or using it for normal, trusted web activity does not initiate the flaw.

Do I need to worry about this if I use Chrome on my mobile device?

According to Halo Surface Signal, this vulnerability is considered 'Very unlikely' to pose a broad infrastructure risk. Because it is a client-side application and not a network-facing service or gateway, it does not present a standard internet-accessible attack surface. Your concern level should focus on individual mobile endpoints rather than server-side infrastructure protection.

How should I respond to CVE-2026-121077?

Your first step is to identify which mobile devices in your environment have the affected browser version installed. Once you have a list of potentially impacted users, prioritize updating their mobile applications to the patched version. Focus coordination efforts on your endpoint security and user-facing application teams to ensure the browser software is brought up to the latest secure release.

References