EUVD-2026-40461
GHSA-3hc5-9533-fp2f
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AC:H and PR:L reflect the required pre-existing renderer compromise, UI:R for loading the crafted page, S:C for the renderer-to-GPU sandbox escape, and high C/I/A from GPU-process code execution.
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionNVD
Use after free in GPU 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 prior to 150.0.7871.47 stems from a use-after-free in the GPU process, letting a remote attacker who has already compromised the renderer break out of the browser sandbox via a crafted HTML page. Google rates the Chromium severity as Critical, and a fix is available in the Stable channel update. …
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 renderer process - the description states the sandbox escape is performed 'via a crafted HTML page' by 'a remote attacker who had compromised the renderer process.' This is a second-stage bug in an exploit chain, not a standalone entry point: a prior renderer-compromise vulnerability is a hard prerequisite. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H, score 9.8) rates this as network-exploitable with no privileges or user interaction, but that generic scoring conflicts with the description, which explicitly requires an attacker to have ALREADY compromised the renderer process before this bug can be used for sandbox escape - a significant precondition the 9.8 does not reflect. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first uses a separate renderer-process vulnerability (e.g., a V8 or Blink bug) to gain code execution inside Chrome's sandboxed renderer when a victim visits a malicious site. From that foothold they send crafted GPU IPC commands from a specially built HTML page to trigger the use-after-free in the GPU process and corrupt memory there, escaping the renderer sandbox into the higher-privileged GPU context. … |
| Remediation | Vendor-released patch: 150.0.7871.47 - upgrade Google Chrome desktop to 150.0.7871.47 or later via the Stable channel and restart the browser to apply, per the 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. |
Recommended ActionAI
Within 24 hours: Identify all endpoints running Chrome versions prior to 150.0.7871.47 and classify by risk. …
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