External risk intelligence

Chrome Payments Use After Free Leads to Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87558

This vulnerability affects a client-side web browser. While it requires a user to visit a crafted HTML page, the vulnerability itself exists within the client application's local processing of web content rather than an internet-facing service, gateway, or externally reachable server infrastructure.

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

This advisory concerns a vulnerability within Google Chrome's payments feature that could allow a remote attacker to execute arbitrary code. While the severity is high, the primary concern is confirming if our systems or users are exposed, as it requires interaction with a crafted web page.

  • Browser flaw allows remote code execution.
  • Understand Chrome's payment processing risk.
  • Confirm relevance and verify user exposure.

Attack Path

How an attacker could exploit the issue

An attacker can trick a user into visiting a malicious webpage, which then exploits a flaw in Chrome's payment processing. This flaw could allow an attacker to execute code on the user's computer, potentially leading to broader system compromise.

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

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a remote attacker could execute arbitrary code outside the sandbox by tricking a user into visiting a crafted HTML page. This could affect system data or user data processed by the browser.

  • System data could be affected.
  • Via a crafted HTML page.
  • Arbitrary code execution outside sandbox.

Operational Fix

Recommended remediation, mitigation, and detection steps

This high-severity vulnerability in Google Chrome's payments component requires immediate attention from teams responsible for endpoint security and user-facing applications. The first practical step is to identify all managed endpoints running affected versions of Chrome, assess their exposure to malicious web content, and confirm ownership for remediation.

  • Endpoint security and application teams own this.
  • Verify Chrome versions and network exposure.
  • Plan and execute Chrome 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 and its Payments component?

Google Chrome is a widely used web browser that renders HTML content and manages user sessions. The Payments component is a built-in feature designed to securely store and process user financial information for online transactions, acting as an interface between the browser's sandbox environment and external payment gateways.

What does a use-after-free vulnerability mean in CVE-2026-87558?

A use-after-free is a memory safety error where a program continues to use a memory address after it has been cleared or freed. In this CVE, the Payments component improperly manages memory, allowing an attacker to manipulate that freed memory space to inject and run malicious code on the host system.

How is this Chrome vulnerability triggered?

This flaw is triggered when a user visits a specifically crafted HTML page designed to interact with the browser's payment processing logic. Simply having Chrome installed is not enough; the malicious code must be actively executed by the browser while processing the crafted page. Browsing legitimate, trusted websites does not trigger this issue.

Is my organization at risk from this Chrome issue?

According to Halo Surface Signal, this vulnerability is considered very unlikely to be a direct infrastructure risk because it resides in client-side software rather than an internet-facing server. Your primary concern is whether endpoints in your environment are running vulnerable versions of Chrome and interacting with untrusted web content.

What should I do to address CVE-2026-87558?

The most effective response is to ensure all managed workstations are updated to the latest stable version of Chrome provided by Google. Since this bug is specific to endpoint software, your team should focus on verifying version numbers across your fleet and ensuring that automated update mechanisms are functioning correctly to patch the Payments component.

References