EUVD-2026-65825
GHSA-xrmp-96p2-c668
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
AV:N and UI:R reflect web delivery requiring user navigation; AC:H reflects mandatory prior renderer compromise; S:U because code execution remains bounded within the existing sandbox.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Buffer overflow in Blink in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Heap-based buffer overflow (CWE-122) in Blink, Chrome's rendering engine, grants native code execution within the renderer sandbox to attackers who have already achieved renderer process compromise, affecting all Chrome versions prior to 152.0.7977.65 across all platforms. The fix is confirmed in stable channel release 152.0.7977.65. …
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 distinct preconditions are both required: (1) the attacker must have already compromised the Chrome renderer process through a separate, independent exploit - this vulnerability is explicitly not an initial-access vector and is only reachable from within an already-corrupted renderer context; and (2) the victim user must actively navigate to or load a crafted HTML page (UI:R per CVSS). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 7.5 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) accurately captures the dual-gated threat model: full renderer-scope compromise is possible, but only after a prior renderer exploit is already in play (AC:H) and user interaction occurs (UI:R). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already leveraged a separate vulnerability to compromise a Chrome renderer process - for example, a V8 JavaScript engine memory corruption bug - serves a crafted HTML page that triggers the Blink heap buffer overflow. The overflow corrupts heap memory within the renderer, redirecting native code execution to attacker-controlled shellcode running inside the Chrome sandbox. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later, as documented in 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, inventory Chrome versions deployed across all endpoints to identify affected installations (versions prior to 152.0.7977.65). …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-122 – Heap-based Buffer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today