External risk intelligence

Chrome iOS Sharing Use-After-Free Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87609

This vulnerability exists in the Sharing component of the Google Chrome browser on iOS. As a client-side end-user application, it is not deployed as a public-facing service, edge gateway, or internet-accessible server. Its exposure is strictly limited to the local environment of the individual device, making network-based public reachability for this specific component inherently unlikely.

Use After Free

Google Chrome

before 153.0.8010.36

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 vulnerability in Google Chrome on iOS could allow attackers to execute code outside of the browser's protected environment using specially crafted network traffic. This means a user could be targeted if they interact with malicious network content through the browser. The main concern at this time is confirming whether this specific vulnerability is relevant to our organization's usage of Chrome on iOS.

  • Remote code execution possible via network traffic.
  • Matters if employees use Chrome on iOS for browsing.
  • Confirm relevance and exposure to our environment.

Attack Path

How an attacker could exploit the issue

An attacker could exploit a use-after-free vulnerability in Google Chrome's Sharing feature on iOS by sending specially crafted network traffic. This could allow them to execute malicious code beyond the browser's security boundaries.

  • Entry condition: Network access to the vulnerable device.
  • Trigger point: Crafted network traffic sent to the Sharing feature.
  • Resulting risk: Arbitrary code execution outside the sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's Sharing component on iOS could allow a remote attacker to execute arbitrary code outside the sandbox when specific, crafted network traffic is received. This may impact the confidentiality, integrity, and availability of the affected device.

  • Arbitrary code execution on the device.
  • Via crafted network traffic.
  • Compromise of device integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Google Chrome on iOS, making application owners and mobile device management teams the primary points of contact. The initial practical step involves identifying all iOS devices running Chrome that are managed or unmanaged, assessing the business criticality of affected users, and confirming ownership for each device or user group before planning remediation efforts.

  • Application and device owners should be accountable.
  • Verify Chrome browser installations on iOS devices.
  • Plan coordinated updates for affected users.

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 iOS and its Sharing component?

Google Chrome on iOS is the mobile version of the web browser, providing users with a platform for accessing online content. The Sharing component is a specific internal feature that handles the process of distributing links or data from the browser to other applications or services on the device.

How does a use-after-free vulnerability work in CVE-2026-87609?

This flaw belongs to the Use After Free (CWE-416) class. It occurs when a program continues to use a memory address after that memory has been cleared or released. An attacker can exploit this by injecting data into that specific memory space, potentially tricking the browser into executing unauthorized commands.

Does browsing normal websites trigger this vulnerability?

No, simply browsing standard websites does not inherently trigger the flaw. The vulnerability requires the browser to process specifically crafted network traffic sent to the Sharing feature. It is not triggered by typical user navigation or interactions with legitimate web content.

Why should I care about CVE-2026-87609 on iOS devices?

You should care because this bug allows code execution outside the browser's sandbox. Halo Surface Signal notes that since Chrome on iOS is a client-side application, it is not a server-side service, so it is unlikely to be exposed to broad, internet-wide automated attacks; however, it remains a risk for individual devices if targeted.

How do I address this Chrome vulnerability?

Your first step is to locate all iOS devices in your environment where Chrome is installed. Once you have identified these assets, focus on ensuring these devices are updated to the latest available version provided by the vendor, which addresses the memory management error.

References