Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H and UI:R reflect the required prior renderer compromise plus crafted-page interaction; S:C with C/I/A:H captures the sandbox escape from renderer to a more privileged process.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Use after free in Media in Google Chrome on Windows prior to 151.0.7922.72 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's Media component on Windows (versions before 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the browser sandbox through a crafted HTML page, exploiting a use-after-free (CWE-416). Rated High by Chromium and CVSS 8.3, it enables a scope-changing escalation from constrained renderer code to broader host access. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the attacker has ALREADY compromised the Chrome renderer process (an explicit prerequisite stated in the CVE description) and can then deliver a crafted HTML page that drives the vulnerable Media code path; the platform is limited to Google Chrome on Windows before 151.0.7922.72. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H, score 8.3) reflects a network-reachable, scope-changing bug with full confidentiality/integrity/availability impact but high attack complexity and required user interaction. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first compromises a Chrome renderer process (for example by chaining a separate renderer-RCE bug), then serves a crafted HTML page that triggers the use-after-free in the Media component to corrupt memory in a more privileged process and escape the sandbox. Given AC:H and the required renderer foothold, this is a realistic component of a two-bug exploit chain rather than a one-click compromise. … |
| Remediation | Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on Windows via the Stable channel, per https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html - restart the browser to ensure the update is applied, since Chrome staging can leave an outdated binary running. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory Chrome instances on Windows devices and verify current version status against 151.0.7922.72 baseline; prepare patch deployment and communications. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-416 – Use After Free
View allSame technique Use After Free
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-50849
GHSA-h5r7-76mx-726x