EUVD-2026-69737
GHSA-qx4r-xfh5-f7gw
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H captures the mandatory renderer pre-compromise prerequisite; S:C and full C/I/A reflect confirmed sandbox escape to host execution.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
6DescriptionCVE.org
Buffer overflow in GPU in Google Chrome on on Windows prior to 152.0.7977.75 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
Stack-based buffer overflow in the GPU component of Google Chrome on Windows (prior to 152.0.7977.75) enables full sandbox escape and arbitrary code execution on the host operating system. Exploitation is a two-stage chained attack: an attacker must first compromise the renderer process (via a separate vulnerability or exploit), then leverage this GPU flaw to break out of Chrome's sandbox and execute code with elevated host privileges. …
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 met: (1) the attacker must have already compromised the Chrome renderer process - this is not a standalone flaw and requires a separate renderer exploit, making fully automated exploitation against uncompromised browsers impossible with this bug alone; (2) the victim must be running Google Chrome on Windows in a version prior to 152.0.7977.75 and must have visited or be visiting attacker-controlled content. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) accurately reflects the attack chain: network-reachable via crafted HTML, but AC:H because exploitation requires a pre-existing compromised renderer - not a standalone one-click bug. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Update Google Chrome on Windows to version 152.0.7977.75 or later immediately; this is the vendor-released patched version per the stable channel advisory at chromereleases.googleblog.com. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, notify Windows Chrome users of the availability of Chrome 152.0.7977.75 or later and initiate deployment through organizational endpoint management tools. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-121 – Stack-based Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today