External risk intelligence

Chrome Web Authentication Use After Free Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87646

The vulnerability exists in a web browser component and requires the user to visit a crafted HTML page. Because web browsers are primary tools for accessing the public internet and are routinely exposed to untrusted external content as part of their normal operation, this attack surface is highly likely to be reachable.

Use After Free

Google Chrome

before 153.0.8010.36

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A recent vulnerability identified in Google Chrome's web authentication feature presents a high risk of allowing remote attackers to execute code outside the browser's security sandbox. This is achievable through malicious web pages, necessitating a review of our exposure to this threat.

  • Attackers can run code by visiting bad websites.
  • It impacts a widely used application, Chrome.
  • Confirm if our users are exposed to this risk.

Attack Path

How an attacker could exploit the issue

An attacker can begin by creating a malicious HTML page. When a user visits this page using a vulnerable browser, it can trigger a use-after-free flaw in the Web Authentication component. Successful exploitation could allow an attacker to execute arbitrary code outside the browser's sandbox, potentially leading to further compromise.

  • Requires user to visit a malicious page.
  • Use-after-free in Web Authentication.
  • Code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's Web Authentication could allow a remote attacker to execute arbitrary code outside the sandbox when a user visits a specially crafted HTML page.

  • Arbitrary code execution outside sandbox.
  • User visits crafted HTML page.
  • Compromise of user's system.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Google Chrome and requires a user to interact with a malicious HTML page. Ownership will likely fall to teams responsible for the browser as an application, potentially the platform or infrastructure teams managing end-user computing environments. The first practical move involves identifying all Chrome deployments, assessing their reachability and criticality, and then coordinating remediation efforts with affected users and any necessary vendor engagement for updates.

  • Browser owners and platform teams.
  • Verify Chrome deployments and user reachability.
  • Plan and coordinate browser 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 Web Authentication component?

Google Chrome is a widely used web browser that renders internet content and executes web applications. The Web Authentication component specifically handles the standards and protocols used for secure login processes, such as managing public key credentials for identity verification when a user interacts with websites.

What does the CWE-416 use-after-free weakness mean for CVE-2026-87646?

A use-after-free weakness occurs when software continues to use a memory pointer after it has been cleared or freed. In this specific vulnerability, an attacker can manipulate this memory error to corrupt the browser's state, which allows them to bypass security protections and execute their own unauthorized code on the system.

How is this Chrome vulnerability triggered?

The flaw is triggered when a user visits a malicious website containing specially crafted HTML. Simply opening the page is sufficient; however, the vulnerability does not trigger if the user never navigates to the attacker's page, or if the browser's Web Authentication component is not invoked during the site visit.

Do I need to worry about this vulnerability in my environment?

Yes, if you use Chrome. According to Halo Surface Signal, this vulnerability is highly likely to be reachable because browsers are designed to constantly process untrusted content from the public internet. Since it allows code execution outside the browser's sandbox, any system running an older version of Chrome is at significant risk.

How should I respond to the Chrome update for CVE-2026-87646?

The most effective first step is to identify all Chrome installations within your organization. Once identified, prioritize updating these browsers to version 153.0.8010.36 or higher. Coordinate with your end-user computing or platform teams to ensure these security updates are deployed across all workstations as quickly as possible.

References