EUVD-2026-40606
GHSA-f7h6-pg9w-wwgv
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Requires a pre-compromised renderer (PR:H) and a chained non-trivial condition (AC:H) plus user interaction (UI:R); successful escape crosses the sandbox boundary (S:C) with full browser-process 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
Insufficient validation of untrusted input in Media in Google Chrome on Windows 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: Medium)
AnalysisAI
Sandbox escape in Google Chrome on Windows before 150.0.7871.47 lets an attacker who has already compromised the renderer process break out of the browser sandbox by serving a crafted HTML page that abuses insufficient input validation in the Media component. Google rates the Chromium security severity as Medium and a fix is shipped in the stable channel, but no public exploit has been identified and EPSS exploitation probability is low at 0.21%. …
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 Chrome renderer process - this is the explicit, stated precondition and the primary limiting factor. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals conflict and must be weighed together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first compromises Chrome's renderer through a separate first-stage bug (e.g., a malicious ad or drive-by page the victim opens), then uses that foothold to deliver a crafted HTML/media payload that abuses the Media component's input validation to escape the sandbox and gain code execution in the higher-privileged browser process. User interaction (visiting the page) is required per UI:R, and no public POC is currently identified, so this is a chained, targeted scenario rather than a mass-exploitation one. |
| Remediation | Vendor-released patch: update Google Chrome for Windows to 150.0.7871.47 or later via the Stable Channel Update described at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html; trigger Chrome's built-in updater (chrome://settings/help) and relaunch, or push the update through enterprise management (Google Update / Chrome Browser Cloud Management) to ensure the browser process actually restarts to apply the fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify and document all Windows systems running Google Chrome versions before 150.0.7871.47. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
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