External risk intelligence

Chrome Extension Use After Free Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87637

This vulnerability exists within the client-side Google Chrome browser's extension framework. It requires a user to navigate to a crafted HTML page, meaning it is a client-side execution issue rather than a service or appliance that is designed to be public-internet-facing or reachable as a network-accessible server.

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 security vulnerability has been identified in Google Chrome's extension framework that could allow a remote attacker to execute code outside of the browser's sandbox. While the technical details involve a "use after free" flaw, the core risk is related to the potential for malicious code execution if a user visits a specially crafted webpage. The main concern at this time is confirming if this vulnerability is relevant to our specific environment and user base, given its client-side nature.

  • Code execution flaw in browser extensions.
  • Requires user interaction; not a direct network threat.
  • Confirm relevance; client-side risks are lower.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage, which then exploits a flaw in Chrome's extension handling. This flaw could allow the attacker to execute code on the user's computer, potentially bypassing security measures.

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

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Google Chrome extensions, when supported by the advisory, could allow a remote attacker to execute arbitrary code outside the browser's sandbox. This could occur when a user visits a specially crafted HTML page, potentially leading to system compromise.

  • Arbitrary code execution outside sandbox.
  • Via a crafted HTML page.
  • System compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Google Chrome extensions, suggesting that application owners and security teams should collaborate. The first practical step is to confirm the presence of affected Chrome versions within the organization, assess exposure by identifying if users are likely to encounter malicious crafted HTML pages, and then coordinate with Chrome update processes.

  • Application owners should investigate usage.
  • Verify user exposure to malicious pages.
  • Coordinate browser update deployment.

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 how do extensions work?

Google Chrome is a widely used web browser that supports extensions, which are small software modules that customize or enhance the browser's functionality. These extensions run within the browser's environment, interacting with web pages and system resources to perform tasks like ad blocking, translation, or productivity enhancements.

What does use-after-free mean in CVE-2026-87637?

A use-after-free, classified as CWE-416, is a memory management error where a program continues to use a memory location after it has been cleared or released. In this CVE, an attacker exploits this flaw to manipulate memory, potentially allowing them to bypass browser security and execute unauthorized code on the user's system.

How is CVE-2026-87637 triggered?

The vulnerability is triggered when a user navigates to a specifically crafted HTML page designed to exploit the browser's extension framework. It does not trigger through background network activity or by simply having an extension installed; it requires the user to interact with the malicious web content.

Why is this Chrome vulnerability relevant?

According to Halo Surface Signal, this is a client-side execution issue, not a server-side flaw. Because it depends on a user visiting a malicious site, it is less likely to impact internal infrastructure directly, but it remains a concern for any environment where employees use Chrome to browse the open internet.

How should I respond to this vulnerability?

Your first step is to verify which devices in your environment are running affected versions of Chrome. Once identified, prioritize updating those browsers to the latest stable release provided by the vendor. This ensures the extension framework is patched against the memory management flaw.

References