External risk intelligence

Chrome Memory Corruption Vulnerability Allows Arbitrary Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-119263

This vulnerability affects a client-side web browser. While it requires a remote attacker to provide a crafted HTML page, the attack surface is the client application itself, not a public-facing service, gateway, or internet-exposed infrastructure. It is classified as client-side software rather than a network-reachable service.

Memory Corruption

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 memory corruption vulnerability was identified in Google Chrome that could allow a remote attacker to execute code outside the browser's security sandbox through a malicious webpage. The vulnerability, classified as critical, requires a user to visit a crafted page to be exploited, suggesting a higher risk when users encounter untrusted content.

  • Browser flaw could let attackers run unauthorized code.
  • Impacts users visiting malicious web pages.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious website, which exploits a memory corruption vulnerability in Chrome's garbage collection. This could allow the attacker to execute code on the user's machine, potentially escaping the browser's sandbox.

  • No authentication or privileges required.
  • Triggered by visiting a crafted HTML page.
  • Risk of code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

A memory corruption vulnerability in Chrome's garbage collection could allow a remote attacker to execute arbitrary code outside the browser's sandbox when a user visits a malicious HTML page. This could affect the confidentiality, integrity, and availability of data processed by the browser.

  • User data and system code at risk.
  • Malicious HTML page opens code execution.
  • Compromised user data and system integrity.

Operational Fix

Recommended remediation, mitigation, and detection steps

Memory corruption in Chrome's garbage collection, prior to version 156.0.8078.79, allows remote code execution. The first practical step is to identify all Chrome instances, determine their reachability and criticality, and assign ownership for remediation.

  • Own Chrome deployments and updates.
  • Verify Chrome version and patch status.
  • Plan targeted Chrome version upgrades.

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 role in this advisory?

Google Chrome is a widely used web browser based on the Chromium open-source project. It manages complex web tasks, including memory management, to render websites and run web applications. This advisory concerns a specific component of Chrome's engine responsible for automatically freeing up memory, known as GarbageCollection, which has been found to have a flaw.

What does memory corruption mean in CVE-2026-119263?

Memory corruption is a weakness class (CWE-119) where a program accidentally accesses or modifies memory it is not supposed to touch. In this CVE, a flaw in how Chrome handles memory cleanup allows an attacker to manipulate that memory process. If successful, this could enable the attacker to run their own unauthorized instructions on the user's computer, potentially bypassing the browser's built-in security sandbox.

How is this Chrome vulnerability triggered?

An attacker triggers this flaw by luring a user to a specially crafted HTML page. When the browser attempts to process the malicious page, the memory corruption occurs. Simply having Chrome installed is not enough to trigger the issue; the vulnerability is only activated if a user actively navigates to a web page specifically designed to exploit this garbage collection defect.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal identifies this as a client-side browser issue rather than a traditional internet-facing server service. Because the vulnerability exists within the client application itself, the risk is tied to user activity—visiting web content—rather than the presence of a public-facing infrastructure service. Your focus should be on endpoints where users browse the web.

How do I address CVE-2026-119263?

The primary response is to update your Chrome installations to version 156.0.8078.79 or later. Since this is a browser-level vulnerability, you should identify all machines in your environment that run Chrome, confirm their current version, and ensure they are patched. Prioritize updates for systems frequently used to access external, untrusted web content.

References