Chrome CVE-2026-126885: A Service Worker Bug With Sandbox Consequences
Google fixed CVE-2026-126885 in Chrome 157.0.8103.78. The defect is a use-after-free in the ServiceWorker component. A remote attacker can trigger it with a crafted HTML page and execute code outside the sandbox, according to the CVE description.
Service workers sit between a page and the network. They persist beyond a page view, intercept fetches, manage caches, and run in a browser-managed lifecycle. That design makes their memory state valuable: a use-after-free here can affect process isolation beyond a tab crash. The security boundary depends on the renderer sandbox continuing to hold even when an attacker can shape web content and service-worker events.
What the advisory establishes
The fixed version is Chrome 157.0.8103.78. Versions before it are listed as affected. The public description says a remote attacker can use a crafted HTML page to execute arbitrary code outside the sandbox. It does not publish a working exploit, and the sources reviewed here do not establish active exploitation of this specific CVE.
The score is high enough to treat the update as an emergency for high-risk browsing profiles. The exposure is harder to reason about on managed endpoints because users may run multiple Chrome channels, packaged applications with embedded browsers, or remote sessions that lag behind the desktop update ring.
Managed browser inventory
Start with the executable version, not the product name in an asset inventory. Collect the Chrome version from user endpoints, virtual desktop templates, release rings, and browser-based kiosks. Check browser extensions and enterprise policies for anything that pins an older channel.
Chrome's own update should be allowed to complete and restart the browser. A long-running session may keep an older process alive after the package update. Verify the running process version, then reopen the browser and confirm that subprocesses use the new build.
For high-value users, temporary hardening can include reducing unnecessary extension permissions, separating sensitive work from unrestricted browsing, and moving administrative tasks into a dedicated browser profile. These measures do not replace the patch. They reduce the chance that a crafted page and a compromised service worker meet in a session with valuable cookies or administrative access.
Investigate a suspected hit
Browser exploitation is difficult to prove from a single crash. Preserve the Chrome version, crash reports, renderer and service-worker logs, downloaded files, extension inventory, and recent profile changes. Review for persistence outside the browser, including scheduled tasks, launch agents, startup folders, and unusual child processes.
A service-worker cache can contain attacker-controlled content long after the original page is closed. Clearing site data for a suspected origin and reopening the browser is reasonable after evidence collection. Do not assume that deleting one tab removes the persistent worker state.
