EUVD-2026-40468
GHSA-ggvw-w797-p3rr
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
AC:H and UI:R because a prior renderer compromise plus victim page load are required; S:C for sandbox escape into the higher-privileged Browser process with full C/I/A impact.
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionNVD
Use after free in Browser 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: Critical)
AnalysisAI
Sandbox escape in Google Chrome desktop versions prior to 150.0.7871.47 lets a remote attacker who has already compromised the renderer process break out of the sandbox and gain broader code execution on the host via a crafted HTML page. Chromium rates the underlying use-after-free as Critical, though there is no public exploit identified at time of analysis and EPSS exploitation probability is low (0.21%). …
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 (e.g., via a prior renderer RCE) - this is an explicit prerequisite stated in the CVE and the single most important limiting factor, meaning this bug cannot be exploited on its own and only functions as the sandbox-escape stage of a multi-bug chain. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The raw CVSS 3.1 base score is 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), which reflects worst-case scope change and full impact, but this overstates standalone risk: the description explicitly requires that the attacker has ALREADY compromised the renderer process, so this is a chain link, not an initial-access bug. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a renderer-level exploit (for example a separate memory-corruption bug) when a victim visits a malicious or compromised website, gaining code execution inside the sandboxed renderer. From that foothold the attacker serves a crafted HTML page that triggers the use-after-free in the Browser process, escaping the sandbox to run code with the browser's higher privileges on the host. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms, as announced in the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); Chrome auto-update normally delivers this, so verify via chrome://settings/help and relaunch to apply. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all systems running Chrome and deploy Chrome 150.0.7871.47 to staging/testing environment. …
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