EUVD-2026-40539
GHSA-m653-2xr7-9jjx
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:L) and chaining plus victim page load (AC:H, UI:R); successful escape crosses into the browser process (S:C) with full host 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
Use after free in Journeys 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 before 150.0.7871.47 stems from a use-after-free in the Journeys (browsing history) component, allowing a remote attacker who has already compromised the renderer process to break out of the sandbox and gain broader code execution on the host via a crafted HTML page. Rated High severity by Chromium and CVSS 9.6, a fix is available from vendor; no public exploit identified at time of analysis and EPSS exploitation probability is low (0.21%, 11th 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 Chrome renderer process - this is the explicit precondition in the CVE description and the primary limiting factor, making this a chained, second-stage sandbox-escape rather than a standalone remote exploit. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The raw CVSS 3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) looks critical, but the description materially qualifies it: exploitation requires an attacker who 'had compromised the renderer process' already, so PR:N reflects the untrusted-web-page entry point rather than a genuinely single-shot remote exploit - this is a second-stage sandbox-escape bug, not a standalone RCE. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first compromises a Chrome renderer process using a separate memory-corruption bug (e.g., via a malicious ad or drive-by page the victim visits), then delivers crafted HTML/IPC data that triggers the use-after-free in the browser-process Journeys code to escape the sandbox and run code with browser-process privileges. No public exploit has been identified at time of analysis, and the low complexity (AC:L) means that once the renderer is owned, the escape itself is straightforward for a skilled attacker. |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms via the Chrome Releases Stable Channel advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); relaunch the browser to apply the update since Chrome staged updates only take effect after restart. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Chrome deployments in your environment and validate current version levels. …
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