EUVD-2026-40532
GHSA-8rcv-2v9q-9vhm
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Requires a pre-compromised renderer plus a UAF race and a user-loaded page, so AC:H and UI:R; the sandbox escape crosses the trust boundary (S:C) with total impact on the browser process.
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 USB in Google Chrome on Mac 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 for macOS before 150.0.7871.47 lets an attacker who has already compromised the renderer process break out of the browser sandbox by exploiting a use-after-free in the USB subsystem via a crafted HTML page. Rated High by Chromium and CVSS 9.6, it functions as a second-stage escalation primitive rather than a standalone entry point. …
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 (a prior, separate renderer RCE is a hard prerequisite), that the victim runs the macOS build of Chrome prior to 150.0.7871.47, and that the victim loads attacker-controlled HTML (UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are deliberately mixed and should 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 gains renderer code execution through a separate bug (e.g., a V8 or DOM flaw) when the victim opens a malicious page, then serves crafted HTML/JS that drives the vulnerable USB code path to trigger the use-after-free and pivot out of the sandbox into the browser process. Once the renderer is owned, attack complexity is low, so a reliable exploit would grant higher-privilege execution on the host; no public PoC is currently identified. |
| Remediation | Vendor-released patch: 150.0.7871.47 - update Chrome on macOS to 150.0.7871.47 or later via the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html), then fully restart the browser so the new binary loads. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Enumerate Chrome versions across all macOS endpoints using your MDM platform and confirm Chrome 150.0.7871.47 or later is available in your software distribution system. …
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