EUVD-2026-65769
GHSA-crjf-9g4f-hqg8
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered crafted traffic exploits UAF requiring prior renderer compromise (AC:H); scope change (S:C) reflects sandbox escape with full CIA impact.
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
Use after free in Chromoting 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 crafted network traffic. (Chromium security severity: High)
AnalysisAI
Use-after-free in Google Chrome's Chromoting (Chrome Remote Desktop) component on Windows enables a remote attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code at the browser or OS level via crafted network traffic. All Chrome versions prior to 152.0.7977.65 on Windows are affected. …
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 concrete preconditions: (1) the target system must have Chrome Remote Desktop (Chromoting) actively in use on Windows - this is not a default Chrome feature and requires deliberate installation and session establishment; (2) the attacker must have already achieved compromise of the Chrome renderer process, which itself typically requires a separate renderer-level vulnerability to be chained. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 score reflects a high-severity, network-reachable sandbox escape with full confidentiality, integrity, and availability impact, but two signals meaningfully temper real-world urgency. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already compromised the Chrome renderer process on a Windows endpoint - for example, via a separate browser vulnerability triggered by a malicious web page - sends crafted Chromoting protocol network traffic to the active remote desktop session. The malformed traffic triggers a use-after-free condition in the Chromoting component, allowing the attacker to corrupt freed heap memory and redirect execution flow. … |
| Remediation | The primary fix is upgrading Google Chrome on Windows to version 152.0.7977.65 or later, available via Chrome's built-in update mechanism or enterprise deployment tooling; the vendor patch is confirmed by 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, identify and communicate to IT and end-user teams all Windows systems using Google Chrome Remote Desktop and explain patch urgency. …
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