EUVD-2026-40705
GHSA-6w32-jgxr-c8j8
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Requires a pre-existing renderer compromise (PR:H) and reliable chaining plus user interaction (AC:H, UI:R); sandbox escape changes scope (S:C) exposing browser-process data (C:H/I:H), with no clear availability 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
Inappropriate implementation in Navigation 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: Medium)
AnalysisAI
Sandbox escape in Google Chrome's Navigation component before 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. Rated Medium by Chromium but carries a 9.6 CVSS due to the scope-changing sandbox breach; EPSS is low (0.17%, 7th percentile) and there is no public exploit identified at time of analysis, indicating it is realistically a second-stage link in an exploit chain rather than a standalone remote-code path.
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 - this is the explicit precondition stated in the CVE description and is the single most important limiting factor: the bug is a sandbox-escape primitive, not an initial-access vector. … 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 lands a separate renderer-level exploit (e.g., via a malicious ad or compromised site) to gain code execution inside Chrome's sandboxed renderer, then serves a crafted HTML page that abuses the Navigation flaw to escape the sandbox and reach the higher-privileged browser process, exposing sensitive data and enabling deeper compromise. The victim need only visit or interact with the malicious page (UI:R). … |
| Remediation | Vendor-released patch: upgrade Google Chrome to 150.0.7871.47 or later on all desktop platforms; verify via chrome://settings/help and relaunch to apply, as documented 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
24 hours: Begin testing Chrome 150.0.7871.47 patch and assess auto-update mechanisms or managed rollout capabilities. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-693 – Protection Mechanism Failure
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