Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered crafted page needs no privileges (PR:N) but requires the victim to open it (UI:R); sandbox escape changes scope (S:C) with full host impact (C/I/A:H).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Media in Google Chrome on Windows prior to 151.0.7922.109 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome's Media component on Windows (versions prior to 151.0.7922.109) lets a remote attacker break out of the renderer sandbox by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated High by Chromium and CVSS 9.6 because a successful escape yields full confidentiality, integrity, and availability impact beyond the sandboxed process. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though Chrome UAF media bugs are historically attractive targets.
Technical ContextAI
The defect lives in Chrome's Media subsystem, the pipeline responsible for decoding and rendering audio/video content delivered through HTML (e.g., <video>/<audio> elements, Media Source Extensions, and codec handling). CWE-416 use-after-free means an object in this pipeline is freed while a dangling pointer to it remains reachable; subsequent use of that pointer allows an attacker who controls heap layout to redirect execution or corrupt memory. Because the reported impact is a sandbox escape with a changed scope, the bug is powerful enough for code running in the media/renderer context to affect the host process boundary. No CPE strings were supplied, but the EUVD affected-version data ('Chrome 151.0.7922.109 <151.0.7922.109') and the Chrome stable-channel advisory scope this to the Windows desktop build.
RemediationAI
Vendor-released patch: Google Chrome 151.0.7922.109 for Windows - upgrade to this build or later via Chrome's built-in updater (chrome://settings/help) and relaunch to apply, per the stable-channel advisory (https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html). In managed environments, push the update through your Chrome enterprise policy/update infrastructure and force a browser restart, since the fix is inert until relaunch. If patching cannot be completed immediately, compensating controls include restricting browsing to trusted sites via enterprise URL allow-listing and disabling autoplay/untrusted media where feasible to reduce exposure of the Media pipeline - with the trade-off of degraded user experience and no guarantee the UAF is unreachable through other media paths. Users of Chromium-based browsers should apply the equivalent vendor build once released. No standalone workaround fully substitutes for the patch.
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: CriticalShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-54137
GHSA-j855-4985-fgj7