External risk intelligence

Chrome for Android Use After Free in Sessions Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-79129

The vulnerability exists within the client-side Google Chrome browser on Android and requires specific user interaction with the UI to exploit. It is not an internet-facing service, gateway, or externally reachable management surface.

Use After Free

Google Chrome

before 152.0.7977.65

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 security vulnerability has been identified in Google Chrome for Android, potentially allowing remote attackers to execute code outside the browser's security sandbox through user interaction and social engineering.

  • Attackers could run unauthorized code on devices.
  • Matters because it affects widespread user software.
  • Confirm relevance and exposure to affected users.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into interacting with a specially crafted web page, leading to the execution of arbitrary code outside the browser's sandbox. This is possible due to a use-after-free vulnerability in the Sessions component of Google Chrome on Android.

  • Social engineering to entice user interaction.
  • Vulnerable Sessions component in Chrome.
  • Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome on Android could allow a remote attacker to execute arbitrary code outside the sandbox. This is possible when a user interacts with the UI, following social engineering, and when supported by the advisory.

  • Arbitrary code execution outside sandbox.
  • Attacker uses social engineering and UI interaction.
  • Compromised user device and potential data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome on Android requires user interaction and social engineering for exploitation, making it unlikely to be an immediate threat to internet-facing services. The primary responsibility lies with teams managing end-user devices and browser deployment, as well as potentially the application owners if specific business apps rely on the browser's sandbox. The first step is to identify affected devices and users, assess the risk based on social engineering likelihood and device criticality, and then coordinate remediation through standard update processes or vendor engagement.

  • Own by endpoint management or device owners.
  • Verify user engagement and device reachability.
  • Plan updates during scheduled maintenance.

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. It includes a Sessions component responsible for managing browser history, tabs, and navigation states. This component runs within a security sandbox designed to prevent websites from accessing other parts of your device, ensuring that web content remains isolated from your personal files and the underlying operating system.

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

CWE-416 refers to a 'Use After Free' vulnerability. In this context, it means the browser's Sessions component mistakenly attempts to access or use memory space that it has already released or cleared. Because the software does not properly handle this memory management error, an attacker can manipulate the process to perform unintended actions, such as running unauthorized code.

How does an attacker trigger this Chrome vulnerability?

An attacker cannot exploit this bug automatically by simply having you visit a page. It requires the attacker to use social engineering to trick you into interacting with a specific part of the browser's user interface. If you do not perform the requested UI interaction, the sequence necessary to trigger the memory error is not completed, and the exploit does not take place.

Why does Halo Surface Signal label this as unlikely?

Halo Surface Signal labels this unlikely because the vulnerability resides in a client-side mobile browser, not an internet-facing server or gateway. Since it cannot be triggered remotely without the user physically engaging with the browser's interface, it does not present the same type of constant, automated risk as a vulnerable network-connected service.

How should I respond to this Chrome security notice?

If you are responsible for managing devices, start by identifying systems running Chrome versions older than 152.0.7977.65. Since this issue requires social engineering, your immediate priority is to ensure these devices are updated to the latest version through your standard deployment channels. Focus on educating users about the risks of interacting with suspicious UI elements while the update is being applied.

References