Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-reachable via any crafted web page, no privileges needed, user must visit the page, sandbox containment holds scope unchanged, full C/I/A within the renderer process.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Compositing in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Use-after-free in Google Chrome's Compositing engine (all versions prior to 152.0.7977.65) enables remote code execution within the Chrome renderer sandbox when a user visits a crafted HTML page. The CVSS 8.8 score reflects full confidentiality, integrity, and availability impact, but execution is sandbox-confined and Chromium's own severity rating is Medium, suggesting real-world exploitation complexity is non-trivial. …
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 a user actively visits a crafted HTML page using a vulnerable version of Google Chrome (prior to 152.0.7977.65) on a desktop platform - user interaction (UI:R) is a hard prerequisite and mass automated exploitation is not feasible. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) places this squarely in the high-severity band, driven by network reachability and full C/I/A impact, but the unchanged scope metric (S:U) is the critical moderating factor - code execution is sandboxed. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers a domain and hosts a crafted HTML page engineered to trigger the use-after-free in Chrome's Compositing engine during layer composition - for example, via JavaScript-driven DOM mutations timed to cause a compositor object to be freed and then accessed. The attacker distributes the URL via phishing email or malvertising; when a user on a vulnerable Chrome version visits the page, the freed memory is accessed, enabling arbitrary code execution within the Chrome renderer sandbox. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later using the browser's built-in update mechanism (chrome://settings/help) or via enterprise deployment tooling; the vendor-released patch is confirmed in the stable channel advisory at https://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, assess the scope of Chrome deployments across your organization and communicate the availability of Chrome 152.0.7977.65 to stakeholders. …
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
EUVD-2026-65860
GHSA-rr84-jj99-3vqg