External risk intelligence

Chrome Use After Free Vulnerability in Views Component Allows Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-78945

The vulnerability affects Google Chrome, a web browser that is designed to be public-facing by default as it actively navigates and interacts with untrusted content from the internet.

Use After Free

Google Chrome

before 152.0.7977.65

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A use-after-free vulnerability in Google Chrome's Views component could allow attackers to execute code outside the browser's sandbox by tricking users into visiting a malicious webpage. The severity of this issue is rated as Critical.

  • Flaw lets attackers run code outside browser sandbox.
  • Critical risk if users visit malicious websites.
  • Confirm relevance and verify browser exposure.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage. This page would exploit a use-after-free flaw in Chrome's Views component. If successful, this could allow the attacker to execute code on the user's computer outside of the browser's security protections.

  • No special access needed.
  • Malicious website.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Google Chrome's Views component could allow a remote attacker, through social engineering and a malicious webpage, to execute arbitrary code outside the browser's sandbox. This could impact the confidentiality, integrity, and availability of the user's system.

  • User's system and data.
  • Malicious webpage and social engineering.
  • Arbitrary code execution outside sandbox.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Google Chrome, meaning ownership likely resides with teams managing user-facing applications and endpoints. The immediate priority is to identify all Chrome instances, assess their exposure and criticality, and confirm the accountable owner for remediation. Planning for updates should consider user impact and vendor coordination.

  • Owner: Endpoint or application owners.
  • Verify: Reachability and business criticality.
  • Action: Plan and coordinate updates.

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 the Views component?

Google Chrome is a widely used web browser that renders web pages and applications. The Views component is a specific part of the browser's framework responsible for handling and displaying user interface elements. This vulnerability affects the way Views manages memory, which is essential for the browser to interact safely with the various websites you visit daily.

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

This is a memory corruption issue classified as CWE-416. It occurs when a program continues to use a memory address after that memory has been freed or cleared. In this case, an attacker can manipulate this freed memory to gain control over the browser's execution flow, effectively tricking the software into performing unintended actions.

How does an attacker trigger this vulnerability?

An attacker must use social engineering to trick a user into visiting a specially crafted, malicious HTML page. This specific browser flaw is not triggered by simply having the software installed or running in the background; it requires an active user interaction with malicious content that leverages the flaw in the Views component.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal indicates this vulnerability is very likely to be relevant because Google Chrome is inherently designed to be public-facing. Since the browser regularly navigates to and interacts with untrusted content from the internet, any device running an outdated version of Chrome is potentially exposed to this remote attack vector.

Do I need to update my software to address this?

Yes. The primary response is to ensure your browser is updated to version 152.0.7977.65 or later, which contains the necessary security patches. Owners of endpoints or applications should inventory their environments to identify and update all instances of Chrome to restore the browser's intended security protections.

References