Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered malicious page (AV:N, PR:N) needs a user to visit it (UI:R); sandbox escape crosses a trust boundary (S:C) yielding full code-execution impact (C/I/A:H).
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Improper input validation in Dawn in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox-escaping remote code execution in Google Chrome's Dawn (WebGPU) component affects all desktop builds prior to 152.0.7977.65, letting a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox and run arbitrary code in a higher-privilege context. Rated 9.6 (Critical) with scope change, it requires only that the user visit a malicious page. …
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 victim to open an attacker-controlled HTML page in a vulnerable Chrome build (< 152.0.7977.65) with WebGPU/Dawn reachable - i.e., GPU-accelerated rendering and WebGPU support enabled, which is the default on supported hardware. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals partially conflict in the usual way for browser bugs: CVSS 3.1 is 9.6 Critical (AV:N/AC:L/PR:N/UI:R/S:C, full C:H/I:H/A:H) because a network-delivered page can escape the sandbox with no privileges, but EPSS is only 0.25% (16th percentile) and the bug is not on CISA KEV, indicating no observed mass exploitation yet. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a malicious web page (or serves it via a compromised ad or iframe) containing crafted WebGPU/Dawn calls, then phishes or otherwise entices a victim into visiting it. When the page loads, the malformed input passes the renderer's checks but corrupts state in the GPU process, giving the attacker code execution outside the renderer sandbox. … |
| Remediation | Vendor-released patch: update Google Chrome to 152.0.7977.65 or later (Stable channel), then fully restart the browser so the new binary and GPU process are loaded; verify via chrome://settings/help. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Chrome deployments across Windows, macOS, and Linux endpoints and prioritize patching for machines with sensitive data access or elevated privileges. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65791
GHSA-9425-vrf6-3vcg