Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Use after free in ServiceWorker in Google Chrome prior to 149.0.7827.53 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. (Chromium security severity: Medium)
AnalysisAI
Remote code execution in Google Chrome versions prior to 149.0.7827.53 stems from a use-after-free condition in the ServiceWorker component that can be triggered by a malicious browser extension. An attacker who convinces a user to install a crafted Chrome Extension can achieve arbitrary code execution within the renderer context. No public exploit has been identified at time of analysis and EPSS exploitation probability is very low at 0.01%, but the high CVSS score (8.8) reflects the severe potential impact.
Technical ContextAI
The vulnerability resides in Chrome's ServiceWorker implementation, a background script technology defined by the W3C Service Worker specification that enables features like offline support, push notifications, and resource caching by intercepting network requests. The root cause is CWE-416 (Use After Free), a memory corruption class in which freed memory is referenced again, allowing attackers to manipulate heap layout and hijack control flow. Chrome ServiceWorkers run within the browser's multi-process sandboxed architecture, but a successful UAF exploit in this component can still yield code execution within the renderer process, often serving as a stepping stone toward sandbox escape chains. The bug was reported through Google's internal CVE program (chrome-cve-admin@google.com) and tracked in Chromium issue 505068950.
RemediationAI
Vendor-released patch: update Chrome to version 149.0.7827.53 or later via the Stable Channel auto-update mechanism, per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprise administrators should verify auto-update is enabled via the ChromeRolloutOverride or RelaunchNotification policies and force a relaunch on managed endpoints. As compensating controls until patching completes, enforce an extension allowlist via the ExtensionInstallAllowlist Chrome enterprise policy to prevent installation of arbitrary extensions (trade-off: blocks legitimate user-requested extensions and requires admin review workflow), or set ExtensionInstallBlocklist to '*' combined with a curated allowlist. Users of Chromium-derived browsers (Edge, Brave, Opera, Vivaldi) should monitor their respective vendor advisories for the corresponding update.
Same weakness CWE-416 – Use After Free
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34662
GHSA-9pgr-9977-jg98