EUVD-2026-40518
GHSA-pwc7-4hq7-rg87
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Delivered over the network via a crafted page (AV:N, UI:R); race-dependent use-after-free gives AC:H; sandbox escape crosses trust boundaries so S:C with total C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Headless 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 Headless component (versions prior to 150.0.7871.47) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox by serving a crafted HTML page. Rated High by Chromium and CVSS 8.3, it is a CWE-416 use-after-free with no public exploit identified at time of analysis; EPSS is low at 0.21% (11th percentile) and CISA SSVC records no known exploitation.
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 renderer process (as the CVE description explicitly states) and is running Chrome's Headless component, then delivers a crafted HTML page - so this is a chained, second-stage sandbox escape rather than an initial-access flaw. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals point to a serious but not urgent issue. … 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 via a separate renderer RCE bug in the same chain), then serves a crafted HTML page that triggers the Headless use-after-free to corrupt memory in the browser process and escape the sandbox onto the host. Given AC:H and UI:R, success depends on winning a memory-reallocation race and on the victim loading the malicious page; no public exploit is identified at time of analysis. |
| Remediation | Vendor-released patch: 150.0.7871.47 - update Google Chrome to 150.0.7871.47 or later on all platforms via the Stable channel and relaunch the browser to apply it, per Google's advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory Chrome and Chromium deployments, prioritizing headless instances used in automation, CI/CD, and testing. …
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 allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today