Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Use after free in UI in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome on Windows versions prior to 148.0.7778.216 allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a use-after-free flaw in the UI component, triggered by a crafted HTML page. Chromium rates this High severity and a vendor patch is available, though no public exploit has been identified at time of analysis and EPSS exploitation probability is very low (0.03%, 11th percentile).
Technical ContextAI
The flaw is a CWE-416 Use-After-Free in the UI subsystem of Chromium's browser process on Windows, affecting Google Chrome as identified by CPE cpe:2.3:a:google:chrome. Use-after-free conditions occur when memory is freed but a dangling pointer continues to be dereferenced, allowing an attacker to control the contents of the reused allocation and corrupt object state - frequently leveraged in Chromium exploit chains to escape the renderer sandbox into the more-privileged browser process where UI handling resides. Because UI code runs in the privileged browser process, a successful exploit crosses the sandbox security boundary that normally isolates web content.
RemediationAI
Vendor-released patch: Google Chrome 148.0.7778.216 for Windows - upgrade to this Stable channel build or later via the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html. In managed environments, force the update via Google Update / Chrome Browser Cloud Management and verify chrome://settings/help reports the patched version after restart. Until users restart the browser the fix is not active, so enforce a relaunch policy (RelaunchNotification / RelaunchNotificationPeriod). If patching is temporarily blocked, compensating controls include restricting browsing to a curated allowlist via URLAllowlist/URLBlocklist policies and enabling Enhanced Safe Browsing to reduce exposure to malicious HTML payloads; note that allowlisting breaks general web use and Safe Browsing does not block targeted exploit pages, so neither substitutes for the update.
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-33079
GHSA-fvmq-6rjr-5xgg