Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered crafted page with UI:R and high-complexity heap exploitation; the required prior renderer compromise is modeled as an attack condition (AC:H) rather than PR, and the sandbox escape yields S:C with total C/I/A impact.
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 Compositing 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 Compositing component (versions prior to 151.0.7922.72) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox and gain broader code execution via a crafted HTML page. Rated Critical by Chromium and CVSS 8.3 (scope-changing use-after-free, CWE-416), it is a second-stage bug that presumes an existing renderer compromise rather than a standalone entry point. …
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 Chrome's renderer process (a prior renderer-code-execution primitive is a hard prerequisite stated in the description) and then delivers a crafted HTML page that is rendered by the victim, so user interaction (navigating to/loading the malicious content) is required. … 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, 8.3 High) reflects network reach, high attack complexity, required user interaction (visiting a page), and a scope change into a total-impact sandbox escape - which aligns with CISA SSVC's 'Technical Impact: total'. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer vulnerability to run code inside Chrome's sandboxed renderer, then serves or navigates the victim to a crafted HTML page that triggers the use-after-free in the Compositing code to corrupt memory across the sandbox boundary and execute code in the higher-privileged browser process. No public POC is identified at time of analysis, and the high attack complexity plus required user interaction make this a second-stage component of a chained exploit rather than a one-shot drive-by. |
| Remediation | Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on all desktop platforms (Chrome's built-in updater delivers this automatically; force it via chrome://settings/help and relaunch to apply). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Immediately initiate an audit of all Chrome installations to identify versions prior to 151.0.7922.72 within the next 24 hours. …
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
EUVD-2026-50776
GHSA-hcvj-frqw-68mv