External risk intelligence

Chrome for Android Use After Free Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-78937

The vulnerability resides in a client-side web browser. While browsers interact with the internet, a successful exploit requires a user to navigate to a crafted page, typically involving social engineering. It is not an internet-facing service, appliance, or gateway that is exposed by design or directly reachable without user interaction.

Use After Free

Google Chrome

before 152.0.7977.65

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves a flaw in Google Chrome on Android that could allow a remote attacker to execute code outside the browser's security sandbox through a malicious website. While the exploit requires user interaction via social engineering, the potential for code execution outside the sandbox warrants attention to confirm relevance.

  • Flaw in Android Chrome allows code execution.
  • Confirms exposure and relevance to our environment.
  • Understand browser risks and user interaction.

Attack Path

How an attacker could exploit the issue

An attacker can trick a user into visiting a malicious webpage using social engineering. This webpage exploits a use-after-free vulnerability in Chrome on Android. If successful, this could allow the attacker to execute arbitrary code outside the browser's sandbox.

  • Requires user to visit a malicious site.
  • Triggered by a crafted HTML page.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome on Android could allow a remote attacker, through social engineering, to execute arbitrary code outside the browser's sandbox when visiting a crafted HTML page.

  • Browser data could be at risk.
  • Social engineering could trigger exposure.
  • Arbitrary code execution is possible.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Google Chrome on Android. The first practical step is to identify all Android devices with Chrome, determine their reachability and criticality, and locate the accountable owner for remediation planning.

  • Identify affected Chrome on Android instances.
  • Verify user interaction is required for exploit.
  • Plan remediation based on exposure risk.

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 a widely used mobile web browser that allows users to navigate the internet, render complex web pages, and run web applications on devices running the Android operating system.

What does use-after-free mean in CVE-2026-78937?

This is a memory management weakness, classified as CWE-416. It occurs when a program continues to use a memory location after it has been cleared or freed. If manipulated, this can allow a remote attacker to corrupt memory and potentially run their own unauthorized commands on the underlying device.

How is this vulnerability triggered?

An attacker must successfully lure a user to a specially crafted malicious HTML webpage, typically through social engineering. Simply having the browser installed is not enough; the bug does not trigger by itself or through passive background processes.

Is my device at risk based on Halo Surface Signal?

According to Halo Surface Signal, the risk is classified as unlikely. Because Chrome is a client-side application and not a public-facing service, it is not directly reachable by attackers. Success relies heavily on deceiving a user into visiting a specific site.

How should I respond to CVE-2026-78937?

Begin by auditing your environment to identify all Android devices running Chrome versions earlier than 152.0.7977.65. Once identified, prioritize updating these instances to the patched version through the official app store to secure the browser against this memory flaw.

References