EUVD-2026-40475
GHSA-63x7-945p-47jj
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Requires prior renderer compromise plus a crafted page and user interaction, so AC:H and UI:R; sandbox escape yields scope change (S:C) with total C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
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 GPU in Google Chrome prior to 150.0.7871.47 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's GPU process (versions prior to 150.0.7871.47) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page. Rated High by Chromium and CVSS 9.6 due to a scope-changing (S:C) full-impact outcome, this is a use-after-free (CWE-416) memory-corruption bug. …
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 - that prior renderer control is the explicit precondition stated in the CVE and is what makes this a sandbox-escape (second-stage) bug rather than initial access. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The 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 lands a separate renderer-process compromise (e.g., via a distinct Chrome bug), then serves the victim a crafted HTML page that drives malicious GPU/Mojo operations to trigger the use-after-free in the GPU process and escape the sandbox onto the host. Given UI:R, the victim must open the attacker-controlled page; no public POC is currently known, and the multi-stage requirement (prior renderer control) makes this a targeted, chained operation rather than a drive-by. |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on the Stable channel, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); Chrome's auto-update normally delivers this, so ensure clients are not blocking updates and force a relaunch to apply it. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all systems running Chrome versions prior to 150.0.7871.47 and develop a prioritized patching schedule. …
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 Memory Corruption
View allShare
External POC / Exploit Code
Leaving vuln.today