External risk intelligence

Chrome Extension Use After Free Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-87504

The vulnerability involves a crafted Chrome extension requiring user interaction and social engineering to execute. While web browsers are internet-facing, the requirement for a user to install or interact with a specific malicious extension limits the exposure compared to services that are automatically reachable or publicly exposed by default.

Use After Free

Google Chrome

before 153.0.8010.36

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Google Chrome could allow a remote attacker to execute code outside the browser's security protections through social engineering and a malicious extension. The main concern is confirming relevance and exposure.

  • Flaw in Chrome lets attackers run unauthorized code.
  • Social engineering and malicious extensions are the method.
  • Confirm relevance and exposure to potential risks.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into installing a malicious Chrome extension. This extension would then allow the attacker to execute code on the user's computer, escaping the browser's security sandbox.

  • Requires user interaction and social engineering.
  • Triggered by a malicious Chrome extension.
  • Risk of arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Google Chrome could allow an attacker to execute arbitrary code outside the browser's sandbox. This could occur when a user is tricked into installing or interacting with a malicious Chrome extension, potentially leading to the compromise of their system.

  • Arbitrary code execution in the user's session.
  • Social engineering via malicious extensions.
  • System compromise when supported by advisory.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome requires user interaction through a malicious extension, meaning immediate action may not be necessary for all systems. The first practical step is for security and platform teams to identify where Chrome is deployed, confirm if the affected version is in use, and then assess business criticality and user exposure for prioritization.

  • Ownership: Platform and Security teams.
  • Verify first: Confirm affected Chrome version usage.
  • Action: Plan updates based on risk.

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 the Google Chrome Core component affected by CVE-2026-87504?

The Core component is the central engine of Google Chrome responsible for rendering web pages, executing JavaScript, and managing the browser's security sandbox. It serves as the foundation for the entire browser experience, handling low-level memory operations that allow users to interact with web content. Security vulnerabilities here are particularly significant because they can compromise the integrity of the entire browser application.

How does a use-after-free weakness enable code execution in this CVE?

A use-after-free (CWE-416) occurs when software continues to use a memory location after that memory has been cleared or freed. In this vulnerability, if an attacker can manipulate this freed memory via a malicious extension, they may be able to overwrite data or redirect the browser's execution flow. This allows the attacker to run unauthorized code on the host system, bypassing the security restrictions that normally contain web browsing activities within a safe container.

Does simply browsing the web trigger this Chrome vulnerability?

No, standard web browsing does not trigger this flaw. The exploit path requires a specific precondition: the user must be successfully targeted through social engineering to install or interact with a crafted, malicious Chrome extension. Passive navigation to a website is insufficient to activate the vulnerability, as it depends on the deliberate deployment of a malicious extension within the browser environment.

How does Halo Surface Signal assess the relevance of CVE-2026-87504?

Halo Surface Signal assigns a 'Possible' score because the risk is highly dependent on user behavior rather than automatic exposure. While Chrome is internet-facing, the requirement for social engineering and the installation of a specific malicious extension acts as a significant barrier. Unlike services that are exploitable by default, this vulnerability relies on an attacker tricking a user, which limits the attack surface to environments where such extensions might be introduced.

What is the first step to address this risk if I use Google Chrome?

Begin by auditing your infrastructure to identify which systems are running versions of Google Chrome prior to 153.0.8010.36. Once you have a clear inventory of affected machines, evaluate the potential for users to be targeted by malicious extensions in your specific environment. Use this information to prioritize security updates for high-risk workstations or shared systems, ensuring the browser is moved to a patched version.

References