Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Reachable from a crafted web page (AV:N, UI:R) with a sandbox-crossing scope change (S:C) and full code execution (C/I/A:H); PR:N retained per Chromium browser-context scoring though a prior renderer compromise is a practical prerequisite.
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
Heap buffer overflow in Chromecast 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 desktop versions prior to 150.0.7871.47 stems from a heap buffer overflow in the Chromecast component, letting an 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, but it is a second-stage bug requiring prior renderer control, and there is no public exploit identified at time of analysis (SSVC exploitation: none, EPSS 0.22%). …
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 (an explicit precondition stated in the CVE description) and then delivers a crafted HTML page that exercises the Chromecast component's vulnerable heap allocation. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals here conflict and must be read together rather than off the raw 9.6. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first compromises the Chrome renderer via a separate memory-corruption bug delivered through a malicious or compromised web page, then serves crafted HTML that drives the Chromecast component to overflow a heap buffer and escape the sandbox into the more privileged browser process. Given UI:R, the victim must load the attacker-controlled page; no public exploit code is currently identified, and Chromium rates the severity High. |
| Remediation | Vendor-released patch: Google Chrome 150.0.7871.47 - update to this version or later via the Stable channel (Help > About Google Chrome, then relaunch) as described in the Chrome Releases 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 deployments across the organization and confirm your update mechanism (auto-update, managed rollout, or manual). …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-122 – Heap-based Buffer Overflow
View allSame technique Heap Overflow
View allVendor StatusVendor
SUSE
Severity: Critical| 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
EUVD-2026-40484
GHSA-9wxf-mr7j-397m