EUVD-2026-50796
GHSA-qfg6-74c9-5pcg
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Full sandbox escape gives scope change and total C/I/A, but the description's required prior renderer compromise plus heap grooming justifies AC:H rather than AC:L.
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
4DescriptionCVE.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: High)
AnalysisAI
Sandbox escape in Google Chrome desktop versions prior to 151.0.7922.72 stems from a use-after-free in the Views UI framework, letting a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page. Rated High by Chromium with a CVSS 9.6 due to scope change and total confidentiality/integrity/availability impact, though there is no public exploit identified at time of analysis and CISA SSVC records exploitation status as none. …
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 sandboxed renderer process (an explicit prerequisite in the CVE description) and can then drive a crafted HTML page to trigger the Views use-after-free; per CVSS UI:R, victim interaction such as loading the malicious page is also required. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and must be read together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first gains code execution inside Chrome's sandboxed renderer (for example by chaining a separate renderer RCE bug), then lures or drives the victim to a crafted HTML page that triggers the use-after-free in the Views browser-process code. By grooming the heap and reclaiming the freed object, the attacker escalates out of the sandbox into the more-privileged browser process. … |
| Remediation | Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on the Stable desktop channel, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html); most installations auto-update, so verify via chrome://settings/help and relaunch to apply. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, communicate the critical Chrome CVE-2026-17670 vulnerability and patch availability to end users and IT teams, enabling or enforcing automatic browser updates if not already active. …
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 Denial Of Service
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