External risk intelligence

Use After Free in Chrome Proxy Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-84324

The vulnerability exists within the client-side Google Chrome browser. While it involves processing network traffic, a web browser is a client application, not a public-facing service, gateway, or infrastructure component that would be hosted or exposed for general internet connectivity in a typical deployment.

Use After Free

Google Chrome

before 152.0.7977.75

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 critical vulnerability in Google Chrome's proxy functionality. The flaw could allow a remote attacker to execute code outside the browser's security boundaries by sending specially crafted network traffic. While the potential for code execution is significant, the primary concern is to confirm if this vulnerability affects any part of our environment, given its client-side nature.

  • Allows attackers to run outside browser security.
  • Critical flaw found in Google Chrome's proxy.
  • Confirm if our users and systems are affected.

Attack Path

How an attacker could exploit the issue

An attacker could send specially crafted network data to a user's Google Chrome browser. If the browser processes this data, a flaw in its proxy handling could allow the attacker to run their own code on the user's system, potentially outside the browser's protected environment.

  • Remote attacker, no special access needed.
  • Crafted network traffic processed by proxy.
  • Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's proxy functionality could allow a remote attacker to execute arbitrary code outside the sandbox. This occurs when the browser processes specially crafted network traffic.

  • Arbitrary code execution on the client.
  • Attacker sends malicious network traffic.
  • Compromise of the user's device.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects Google Chrome. Owners of endpoints running Chrome, along with infrastructure and security teams responsible for managing browser deployments and network security, should coordinate. The first step is to identify all endpoints with vulnerable Chrome versions, assess their exposure, and then plan for remediation by coordinating with Chrome release cycles or vendor management.

  • Endpoint owners and security teams.
  • Confirm Chrome version and network reachability.
  • Plan updates based on risk assessment.

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 why does it have a proxy component?

Google Chrome is a widely used web browser that acts as a client application for accessing internet resources. Its proxy component is a built-in feature designed to manage how the browser routes web traffic, allowing it to connect through intermediate servers to reach websites or bypass certain network restrictions.

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

A use-after-free is a memory management error categorized as CWE-416. It occurs when software continues to use a memory location after that memory has been cleared or released. In this specific CVE, the browser's proxy incorrectly handles this memory, which a remote attacker can manipulate to execute unauthorized code on the host system.

How does an attacker trigger the Chrome proxy flaw?

The vulnerability is triggered when the browser processes specifically formatted network traffic. It is important to note that merely having the browser open is not enough; the software must actively receive and interpret the malicious data stream designed to exploit the proxy's flawed memory handling logic.

Do I need to worry about this if Chrome is not a public-facing service?

According to Halo Surface Signal, this is very unlikely to be a high-priority infrastructure risk because Chrome is a client-side application. It is not a public-facing server or gateway; it runs on individual user devices. Your primary concern is the potential impact on end-user endpoints rather than external service compromise.

When should I take action for this browser vulnerability?

You should begin by identifying which endpoints in your environment are running affected versions of Chrome. Once identified, coordinate with your internal teams to plan for software updates in alignment with vendor release cycles, ensuring the browser is patched to a version that contains the necessary security fixes.

References