External risk intelligence

Use After Free in Google Chrome Allows Arbitrary Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113189

The vulnerability exists within the Google Chrome browser and requires a user to navigate to a crafted HTML page. While web browsers are internet-facing applications, exploitation requires specific user interaction (navigating to a malicious site). It is not a service that is inherently public-facing by design in the way an edge gateway or identity portal is, leading to a classification of Possible.

Use After Free

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A use-after-free vulnerability in Google Chrome could allow an attacker to execute arbitrary code outside the browser's security sandbox if a user visits a specially crafted webpage.

  • Allows attackers to run code on user devices.
  • Critical for users interacting with web content.
  • Confirm relevance to understand potential exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious webpage. This webpage would exploit a use-after-free vulnerability in Chrome's rendering engine. If successful, this could allow the attacker to execute code on the user's system, potentially outside the browser's security sandbox.

  • Attacker must present a malicious HTML page.
  • User must visit the crafted page.
  • Arbitrary code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Google Chrome could allow a remote attacker to execute arbitrary code outside the sandbox when a user visits a specially crafted HTML page. This could impact the security and integrity of the user's system.

  • Arbitrary code execution outside sandbox.
  • Remote attacker crafts HTML page.
  • System compromise and data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability, a use-after-free in Chrome's Core, could allow remote code execution via a malicious HTML page. Identifying affected systems, confirming business criticality and reachability, and assigning ownership are the immediate first steps. Then, remediation can be planned based on risk.

  • Ownership likely falls to IT infrastructure and security teams.
  • Verify user exposure to malicious web content.
  • Plan Chrome updates during a maintenance window.

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 in the context of CVE-2026-113189?

Google Chrome is a widely used web browser built on the Chromium engine. It functions as an interface for accessing internet content, managing web applications, and rendering HTML pages. Because it handles complex web code locally on your device, its core components must securely manage memory to prevent malicious websites from gaining control over your computer's operating system.

What does a use-after-free vulnerability mean?

This is a memory management error classified as CWE-416. It occurs when a program continues to use a memory address after that memory has been cleared or freed. An attacker can manipulate this flaw to replace the old data with their own malicious instructions, tricking the browser into executing arbitrary code that should not be allowed to run.

How does an attacker trigger CVE-2026-113189?

The vulnerability is triggered when a user navigates to a specifically crafted HTML page designed to exploit memory mismanagement. Crucially, the bug is not triggered by simply having the browser installed or running; it requires the active rendering of the malicious webpage content to initiate the memory error.

Is my organization at risk from this Chrome vulnerability?

Halo Surface Signal labels this as 'Possible' risk. While Chrome is internet-facing, this flaw requires a user to interact with a malicious link or site to succeed. Because it relies on user navigation rather than an automatic network-level attack, the risk is higher for organizations where users frequently browse untrusted web content or click external links.

How should I respond to this threat?

Prioritize updating all instances of Chrome to version 156.0.8078.47 or later to implement the vendor's security patch. Verify which systems in your environment are running older versions and schedule these updates. Focus your efforts on workstations and systems where employees interact with external web content regularly.

References