Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network vector and no-privileges reflect unauthenticated HTML delivery; high complexity captures mandatory renderer-compromise prerequisite; scope change encodes the sandbox escape to host execution.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds write in Crashpad in Google Chrome on on Windows prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Out-of-bounds write in Chrome's Crashpad crash-reporting library on Windows, versions prior to 152.0.7977.65, enables sandbox escape and arbitrary code execution when chained with a separate renderer compromise. The flaw (CWE-787) is the second stage of a two-stage exploit: an attacker who has already gained code execution inside the sandboxed renderer can trigger the memory corruption in Crashpad to break the sandbox boundary and execute arbitrary code at Chrome process privilege on the host. …
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 | Two sequential conditions must both be satisfied: first, the attacker must have already achieved code execution inside Chrome's sandboxed renderer process on Windows via a separate, independent vulnerability not described in this CVE; second, the target must be running Google Chrome on Windows at a version prior to 152.0.7977.65. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD-assigned CVSS 3.1 score of 8.3 (High) with vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H accurately reflects the chained nature of exploitation: high attack complexity captures the renderer-compromise prerequisite, scope change reflects the sandbox escape, and full C/I/A confidentiality-integrity-availability impact reflects the consequence of executing outside the sandbox. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page that first exploits a separate renderer vulnerability to gain code execution inside Chrome's sandboxed renderer process on a Windows host. From that sandboxed foothold, the attacker triggers the out-of-bounds write in the Crashpad component by causing a crash-related code path to process attacker-controlled data, overwriting adjacent memory to gain control of execution flow outside the sandbox and achieving arbitrary code execution at Chrome process privilege. … |
| Remediation | Upgrade Google Chrome on Windows to version 152.0.7977.65 or later, which constitutes the vendor-released patch per the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit all Chrome installations across Windows systems to establish current version inventory. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-787 – Out-of-bounds Write
View allSame technique Memory Corruption
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65820
GHSA-g6pq-88qr-3vgv