External risk intelligence

Use After Free in Chrome ServiceWorker Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-79056

The vulnerability exists in the ServiceWorker component of a widely used web browser. Exploitation requires a user to visit a crafted HTML page, which is a common activity for internet-facing web browsers. Because browsers are designed to constantly interact with public internet content, the attack surface is frequently exposed to remote, untrusted web traffic.

Use After Free

Google Chrome

before 152.0.7977.65

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A use-after-free vulnerability in the ServiceWorker component of a widely used web browser allows a remote attacker to potentially execute arbitrary code outside its sandbox by luring a user to a crafted webpage. While the Chromium security severity is noted as Low, the attack vector is network-based, requiring only user interaction with a malicious page, which is a common exposure for internet-facing browsers. The primary concern is confirming if this specific browser component is utilized within your environment and if exposure to untrusted web traffic is possible.

  • Browser code flaw can allow external code execution.
  • Wide use means potential for broad, yet indirect, exposure.
  • Confirm browser component relevance and exposure.

Attack Path

How an attacker could exploit the issue

A remote attacker could exploit this vulnerability by tricking a user into visiting a malicious HTML page. This page would interact with a vulnerable ServiceWorker component in the browser. If successful, the attacker could potentially execute code outside the browser's protected sandbox.

  • Requires user to visit a malicious page.
  • Exploits a use-after-free flaw.
  • Allows code execution outside sandbox.

Live Threat

Current exploitation, exposure, and threat context

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

  • Arbitrary code execution in browser.
  • User visits malicious webpage.
  • Sandbox bypass for code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given that this vulnerability affects Google Chrome's ServiceWorker component and can be exploited via a crafted HTML page, the primary responsibility likely falls to teams managing end-user computing environments and the browser itself. The initial step should be to identify all Chrome instances, confirm exposure to untrusted web content, and determine business criticality before planning remediation.

  • Ownership: End-user computing and browser management teams.
  • Verify: Browser reachability and business criticality.
  • Action: Plan phased deployment of browser 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's ServiceWorker component?

ServiceWorkers are scripts that run in the background of your web browser, separate from a web page. They enable features like offline access, push notifications, and background data synchronization. By acting as a proxy between the browser and the internet, they help web applications feel more responsive and capable, even when network connectivity is limited.

What does CVE-2026-79056 mean by use-after-free?

This is a memory management error categorized as CWE-416. It happens when a program continues to use a pointer to a memory location after that memory has been cleared or deallocated. In this case, the browser mistakenly accesses that freed space, which an attacker can manipulate to inject and run their own unauthorized code.

How is this ServiceWorker flaw triggered?

The vulnerability is triggered when a user navigates to a specifically crafted HTML page designed to exploit the memory error. It does not activate simply by having the browser installed or running; the browser must actively process the malicious content provided by the attacker to initiate the improper memory access.

Why should I care about this vulnerability?

According to Halo Surface Signal, browsers are designed to interact with untrusted public internet traffic, making them inherently internet-facing. Because this flaw allows code execution outside the browser's sandbox, any system running an outdated version of Chrome and accessing the web is potentially at risk of unauthorized code execution.

What steps should I take if I use Chrome?

Your first priority is to identify all systems in your environment running versions of Google Chrome earlier than 152.0.7977.65. Once identified, prioritize these systems for browser updates to the latest stable version to ensure the patched ServiceWorker code is active, as this update removes the flawed memory handling logic.

References