EUVD-2026-40664
GHSA-5vj5-q8pj-x572
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L
Network delivery requires no attacker credentials (PR:N), but AC:H reflects the mandatory renderer pre-compromise prerequisite; S:C encodes the sandbox escape; C/I/A:L matches confirmed limited direct impact per description.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L
Lifecycle Timeline
4DescriptionCVE.org
Insufficient data validation in Storage 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 prior to 150.0.7871.47 exploits a heap-based buffer overflow (CWE-122) in the Storage component, enabling an attacker who has already compromised the renderer process to break out of Chrome's sandbox via a crafted HTML page. This is a chained, second-stage vulnerability - renderer compromise through a separate flaw is a hard prerequisite, making standalone exploitation infeasible. …
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 two sequential, non-trivial conditions: first, the attacker must already have compromised the Chrome renderer process through a separate, independent vulnerability - this is explicitly stated in the CVE description and encoded in the CVSS AC:H metric; second, the victim must interact with a crafted HTML page (UI:R), which triggers the Storage heap overflow. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score of 5.8 (Medium) reflects three significant limiting factors encoded in the vector: AC:H (high attack complexity - renderer pre-compromise required), UI:R (victim must navigate to a crafted page), and C:L/I:L/A:L (limited direct confidentiality, integrity, and availability impact per base metrics). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first delivers a JavaScript exploit (via a malicious or compromised web page) that achieves code execution within Chrome's sandboxed renderer process through a separate vulnerability. With renderer control established, the attacker serves a crafted HTML page that triggers the heap-based buffer overflow in Chrome's Storage component, corrupting heap memory structures to escape the renderer sandbox and execute arbitrary code at the OS level under the browser's user account. … |
| Remediation | Update Google Chrome to version 150.0.7871.47 or later, the confirmed vendor-released patch per the Chrome Stable Channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-122 – Heap-based Buffer Overflow
View allSame technique Heap Overflow
View allVendor StatusVendor
SUSE
Severity: Moderate| 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