EUVD-2026-50778
GHSA-wqjr-h479-pxvp
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
AV:N with UI:R since a crafted page is loaded, but AC:H because escape requires a pre-existing renderer compromise; scope changes from renderer sandbox to browser process with high impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Use after free in Views in Google Chrome 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: Critical)
AnalysisAI
Sandbox escape in Google Chrome's Views UI framework (versions prior to 151.0.7922.72) lets a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page. Google rates the Chromium severity Critical (CVSS 9.6), and while a patch is available on the Stable channel, there is no public exploit identified at time of analysis and EPSS estimates exploitation probability at just 0.31%. …
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 renderer process (the description states this explicitly) - this bug is the sandbox-escape stage and cannot be triggered from a clean, uncompromised browser by itself. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a separate renderer-process exploit (for example via a malicious ad or compromised site) to gain code execution inside the sandboxed renderer, then serves a crafted HTML page that drives the browser process into the Views use-after-free, corrupting browser-process memory to escape the sandbox and run code at the browser's higher privilege level. Given AV:N/AC:L/UI:R, the victim only needs to visit or render the attacker-controlled page. … |
| Remediation | Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on the Stable channel, then fully relaunch the browser so the new binary loads (per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory Chrome deployments and their current versions to identify affected systems. …
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