External risk intelligence

Chrome Safebrowsing Use After Free Vulnerability Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-79012

The vulnerability resides within the Safebrowsing component of a client-side web browser. It requires the user to be tricked via social engineering into navigating to a crafted HTML page, making it a client-side issue rather than a public-facing service or infrastructure reachable directly from the internet.

Use After Free

Google Chrome

before 152.0.7977.65

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 critical vulnerability has been identified in Google Chrome's Safebrowsing feature, potentially allowing attackers to execute malicious code on user devices through carefully crafted web pages. This threat requires careful evaluation to understand its relevance to our environment.

  • Flaw allows code execution via web pages.
  • Leadership should track potential user impact.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker could trick a user into visiting a malicious HTML page through social engineering. This crafted page would target a use-after-free vulnerability in the Safebrowsing feature of Google Chrome. If successful, the attacker could execute arbitrary code on the user's machine, bypassing the browser's sandbox security.

  • Social engineering to a malicious page
  • Use-after-free in Safebrowsing
  • Arbitrary code execution outside sandbox

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's Safebrowsing component could allow a remote attacker, through social engineering, to execute arbitrary code outside the browser's sandbox when a user visits a specially crafted HTML page.

  • Arbitrary code execution outside sandbox.
  • Malicious HTML page via social engineering.
  • System compromise and data theft.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Chrome's Safebrowsing component requires a user to interact with a malicious HTML page, making it a client-side issue. Ownership likely falls to teams managing endpoint security and user-facing applications, as the primary remediation involves updating the browser. The first practical step is to identify all endpoints with the affected browser and prioritize those that are business-critical or have a higher risk of social engineering attacks before planning the update.

  • Endpoint and application owners should manage this.
  • Confirm user exposure and browser reachability first.
  • Plan and coordinate browser updates across endpoints.

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 Safebrowsing?

Safebrowsing is a security feature integrated into Google Chrome that checks the web pages you visit against lists of known dangerous sites. It aims to protect users from phishing, malware, and other web-based threats by analyzing site content in real time as you navigate the internet.

What does use-after-free mean in CVE-2026-79012?

This is a memory management flaw categorized as CWE-416. It occurs when a program continues to use a memory location after it has been cleared or deleted. In this case, an attacker can manipulate this confusion to force the browser to run unauthorized instructions instead of legitimate program tasks.

How is this vulnerability triggered?

An attacker must successfully trick a user through social engineering into visiting a specially crafted HTML page. Simply having the browser installed or running in the background does not trigger the flaw. The vulnerability requires active navigation to the malicious content to initiate the memory error.

Is my infrastructure at risk from this CVE?

Halo Surface Signal indicates this is unlikely to impact your server infrastructure. Because the flaw resides within a client-side browser component and requires user interaction, it is not a public-facing service vulnerability that can be scanned or reached directly from the internet by automated attackers.

What should I do to protect my devices?

The primary defense is to ensure Google Chrome is updated to version 152.0.7977.65 or later. Coordinate with endpoint management teams to verify that systems are running the patched version, prioritizing computers used by employees who frequently access external web content.

References