EUVD-2026-65978
GHSA-q9c5-rc4c-8fc9
Severity by source
AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AV:L and AC:H reflect local delivery requiring prior renderer compromise; S:C and C/I/A:H confirm full host-system sandbox escape impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in UI in Google Chrome prior to 152.0.7977.65 allowed a local attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a local program. (Chromium security severity: Medium)
AnalysisAI
Use-after-free in Chrome's UI layer allows a local attacker who has already achieved code execution inside the renderer process to escape the Chrome sandbox and execute arbitrary code on the underlying host system. All Google Chrome desktop releases prior to 152.0.7977.65 are affected per CPE cpe:2.3:a:google:chrome. …
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 two preconditions: (1) the attacker must have already achieved code execution within the Chrome renderer process, typically via a separate, independently exploitable renderer vulnerability - this is the primary gating condition; and (2) user interaction (UI:R) is required to trigger the UI-layer use-after-free, consistent with a user performing some browser action that exercises the vulnerable UI code path. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD CVSS score of 7.7 with vector AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H captures a high-complexity, multi-stage attack: local access vector, high attack complexity (chained renderer compromise required), user interaction needed, and a scope change to the host OS. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer vulnerability (e.g., a type confusion or OOB read in V8 or Blink) to gain code execution inside the sandboxed Chrome renderer process. From there, they craft inter-process communication messages that trigger the use-after-free condition in the browser process's UI component, corrupting freed heap memory to redirect execution flow. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later immediately; this is the vendor-confirmed patched release per the 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 your environment to determine which systems run Chrome versions prior to 152.0.7977.65 and assess the exposure scope. …
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 Use After Free
View allShare
External POC / Exploit Code
Leaving vuln.today