EUVD-2026-40489
GHSA-jmxm-fm2m-r778
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Delivered via crafted web page (AV:N, UI:R); the renderer-compromise prerequisite and unreliable type-confusion trigger justify AC:H; sandbox escape crosses a trust boundary (S:C) with total impact (C/I/A:H).
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Type Confusion in Chrome Tabs 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 lets a remote attacker who has already compromised the renderer process escalate out of the sandbox via a crafted HTML page that triggers a type-confusion bug (CWE-843) in the Tabs component. Exploitation is gated behind prior renderer compromise and user interaction, and the flaw is rated High by Chromium with a CVSS 8.3 due to scope change and total impact. …
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 the attacker to have ALREADY compromised the Chrome renderer process - this is an explicit prerequisite stated in the CVE description and makes the flaw a second-stage sandbox-escape primitive, not a standalone entry point. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and point to a serious-but-not-emergency issue. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first uses a separate renderer exploit (e.g., a V8 or DOM bug) to gain code execution inside a Chrome renderer when the victim visits a malicious page. From that compromised renderer, the attacker delivers crafted HTML/IPC that triggers the type-confusion flaw in the Tabs component, corrupting memory in the higher-privileged browser process to escape the sandbox and run code with the browser's privileges on the host. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms; this is the primary and complete fix, delivered via the stable-channel update at 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
Within 24 hours: Inventory Chrome deployment scope across endpoints and notify users of available security update. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Memory Corruption
View allVendor StatusVendor
SUSE
Severity: Important| 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