EUVD-2026-40730
GHSA-fff7-xvg4-9wc8
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H because exploitation is chained and requires a pre-existing renderer compromise plus specific media-path grooming; UI:R for the crafted page, S:C and C/I/A:H for a full sandbox escape.
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 GetUserMedia 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: Low)
AnalysisAI
Sandbox escape in Google Chrome's GetUserMedia (media capture) implementation before version 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. The flaw is a use-after-free (CWE-416) reported by Google's own security team; despite an NVD CVSS of 9.6, Chromium rates its severity Low, and there is no public exploit identified at time of analysis with an EPSS of only 0.17% (7th percentile).
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 (typically via a separate renderer RCE bug) - this is explicitly stated in the description and is the primary prerequisite; the bug itself is the sandbox-escape stage, not initial access. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals conflict and must be read together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first uses a separate renderer-compromise bug to gain code execution inside Chrome's sandboxed renderer, then lures the victim to a crafted HTML page that drives the GetUserMedia code path to trigger the use-after-free, corrupting browser-process memory to escape the sandbox. No public exploit is identified at time of analysis, so this would be built as the escape stage of a bespoke chain rather than run from an off-the-shelf tool. |
| Remediation | Vendor-released patch: Google Chrome 150.0.7871.47 - update to this version or later via Chrome's built-in updater (Help > About Google Chrome) and relaunch the browser so the new binary loads, which is the complete fix and has no functional trade-off. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
24 hours: Identify and inventory all Chrome installations currently running versions before 150.0.7871.47 in your fleet; escalate findings to endpoint owners. …
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: 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