External risk intelligence

FedCM Use-After-Free in Chrome Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-79078

This vulnerability exists within the FedCM implementation of a web browser client. Exploitation requires a user to navigate to a crafted HTML page, making it a client-side attack surface rather than an internet-facing service, gateway, or appliance that is exposed by design in normal deployments.

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 vulnerability in Google Chrome's FedCM feature could allow an attacker to execute code outside the browser's secure environment through a malicious webpage. This flaw carries a critical severity rating and, while requiring user interaction via social engineering, presents a potential risk if exploited. The primary concern is to confirm if this specific technology is in use within the organization and assess any potential exposure.

  • Flaw allows code execution outside the browser.
  • User interaction is required for exploitation.
  • Confirm relevance and exposure for leadership.

Attack Path

How an attacker could exploit the issue

An attacker can exploit this vulnerability by tricking a user into visiting a malicious webpage. This page would contain specially crafted HTML designed to trigger a use-after-free flaw within Chrome's FedCM component. If successful, an attacker could potentially execute their own code with elevated privileges outside of the browser's security sandbox.

  • Requires user to visit a malicious webpage.
  • Triggered by a crafted HTML page.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A use-after-free vulnerability in Chrome's FedCM could allow a remote attacker to execute arbitrary code outside the sandbox. This may occur when a user is tricked into visiting a malicious HTML page.

  • Arbitrary code execution in the browser.
  • Attacker tricks user into visiting malicious page.
  • Compromised user session or browser data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability impacts Google Chrome's FedCM component, requiring a user to interact with a malicious HTML page to exploit. Responsibility likely falls to the platform or application team managing Chrome deployments and potentially the security team for policy enforcement. The first practical step is to identify all Chrome instances, assess user exposure, and confirm the availability of the updated browser version.

  • Platform and application teams own the issue.
  • Verify Chrome browser version and user exposure.
  • Plan coordinated updates during maintenance windows.

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 the FedCM component in Google Chrome?

FedCM, or Federated Credential Management, is an API built into the Chrome browser that allows websites to manage user identity and authentication through third-party providers. It serves as a privacy-preserving way for users to log into services without needing to share credentials directly with those sites, acting as a middleman for secure sign-on processes.

How does a use-after-free vulnerability work in CVE-2026-79078?

A use-after-free is a memory management error where software continues to use a pointer to a memory address after that memory has been cleared or freed. In this CVE, the flaw allows an attacker to manipulate this dangling pointer to overwrite data or execute unauthorized code, effectively tricking the browser into performing actions it was not intended to support.

Do I need to be logged into a site to trigger this Chrome vulnerability?

No. The vulnerability is triggered by simply visiting a crafted HTML page designed by an attacker. It does not require you to be actively signed into a specific service or interacting with the FedCM prompt itself; merely loading the malicious webpage within the vulnerable browser version is sufficient to initiate the exploit process.

Is CVE-2026-79078 an internet-facing threat?

According to Halo Surface Signal, this is a client-side attack surface rather than an internet-facing service or gateway. Because exploitation requires a user to navigate to a specific malicious page, the risk is primarily tied to end-user browsing behavior rather than the exposure of infrastructure or servers directly connected to the internet.

When should I update Chrome to address this security flaw?

You should prioritize updating Chrome to version 152.0.7977.65 or later immediately. Since this flaw allows for code execution outside the browser's security sandbox, patching is the primary defense. Start by auditing your environment to locate all Chrome installations and coordinate a deployment of the stable channel update to ensure all users are protected.

References