EUVD-2026-65973
GHSA-gx5g-wr9h-pj4c
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AV:N and UI:R because victim must visit a malicious page; AC:H for required renderer pre-compromise; PR:N as no target credentials needed; S:C for sandbox escape to browser 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
7DescriptionCVE.org
Use after free in Views in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Use-after-free in Chrome's Views UI component enables sandbox escape to arbitrary code execution outside the browser sandbox, affecting all Google Chrome versions prior to 152.0.7977.65. Exploitation requires an attacker who has already achieved renderer process compromise - making this a chained, second-stage attack rather than a direct initial access vector. …
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 two sequential conditions to both be satisfied: first, the attacker must have already achieved code execution within Chrome's renderer process (via a separate, unchained vulnerability); second, the victim must interact with a crafted HTML page that triggers the Views use-after-free. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS base score of 8.3 with S:C/C:H/I:H/A:H reflects the severity of the impact - full compromise of the browser process - but AC:H accurately captures the significant prerequisite: prior renderer compromise. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A sophisticated attacker first exploits a separate renderer-level vulnerability (e.g., a JavaScript engine bug) when the victim visits a malicious HTML page, gaining code execution inside Chrome's sandboxed renderer process. The attacker then triggers the Views use-after-free from within the compromised renderer, escalating to execute arbitrary code at the browser process privilege level outside the sandbox, achieving full host-level code execution. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later immediately; this is the vendor-released patch per the official Stable Channel advisory at http://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit Chrome deployment across the organization and establish a staged update plan targeting Chrome 152.0.7977.65 or later as mandatory. …
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 allShare
External POC / Exploit Code
Leaving vuln.today