External risk intelligence

Google Chrome Payments Use After Free Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87474

This vulnerability is a client-side issue within the Google Chrome web browser. While it requires the user to load a crafted HTML page, the vulnerability itself exists within the end-user application rather than a public-facing server, gateway, or internet-exposed service.

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 high-severity vulnerability identified in Google Chrome, specifically a use-after-free issue within its payments component. While a remote attacker could potentially exploit this through a malicious webpage, the impact is primarily on the end-user's browser, allowing for code execution outside of its normal security boundaries. The main concern is confirming if our organization's usage of Chrome aligns with the conditions described.

  • A browser flaw could let attackers run unauthorized code.
  • Users must visit a malicious site for exploitation.
  • Confirm if Chrome usage makes this a relevant concern.

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 flaw in Chrome's payment handling to escape the browser's security sandbox. Successful exploitation could allow the attacker to run their own code on the user's computer.

  • No prior access needed.
  • Malicious HTML page.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in the Payments component of Chrome could allow an attacker to execute arbitrary code outside the sandbox when a user visits a malicious HTML page. This could lead to the compromise of user data or system functions within the browser's isolated environment.

  • Browser sandbox protections.
  • Visiting a crafted HTML page.
  • Arbitrary code execution outside sandbox.

Operational Fix

Recommended remediation, mitigation, and detection steps

This "use after free" vulnerability in Chrome's Payments component requires immediate attention from teams responsible for endpoint security and browser management. The first step is to identify all systems running affected Chrome versions, confirm their exposure to user-initiated web browsing, and determine business criticality. Once identified, engage the accountable system owners to plan and execute remediation.

  • Endpoint and Browser Management Teams own resolution.
  • Verify user-facing systems with active Chrome usage.
  • Coordinate upgrade or patching via established 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 and its Payments component?

Google Chrome is a widely used web browser built on the Chromium engine. The Payments component is an integrated feature designed to handle digital transactions, allowing users to save and auto-fill payment methods like credit cards securely during online checkouts.

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

This is a memory management error (CWE-416) where the software continues to use a pointer to a memory location after that memory has been cleared. In this CVE, an attacker can manipulate this flaw to potentially run unauthorized code on a user's computer.

How does an attacker trigger this vulnerability?

An attacker triggers the bug by convincing a user to navigate to a specifically crafted HTML page. Simply having Chrome installed is not enough; the vulnerability does not trigger if the user avoids visiting malicious or compromised websites.

Do I need to worry if Chrome is not internet-facing?

According to Halo Surface Signal, this is a client-side issue. While it is classified as external due to the network-based attack vector, the risk is concentrated on end-user workstations that browse the internet, rather than internal backend servers.

When should I update my systems for this CVE?

Prioritize updating all endpoints running affected versions of Chrome immediately. Coordinate with your browser management teams to verify current versions across the organization and deploy the stable channel update to ensure the Payments component is patched.

References