Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Chromoting in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code via malicious network traffic. (Chromium security severity: Medium)
AnalysisAI
Remote code execution in Google Chrome versions prior to 149.0.7827.53 is possible through a use-after-free flaw in the Chromoting (Chrome Remote Desktop) component, triggered by malicious network traffic targeting a victim's session. The CVSS 8.8 score reflects high impact across confidentiality, integrity, and availability, though successful exploitation requires user interaction. No public exploit has been identified at time of analysis and EPSS exploitation probability is very low at 0.04%.
Technical ContextAI
The vulnerability resides in Chromoting, the underlying technology powering Chrome Remote Desktop functionality, which handles peer-to-peer remote desktop sessions over the network. CWE-416 (Use After Free) indicates a memory corruption condition where the code continues to reference heap memory after it has been freed, allowing an attacker to manipulate the freed allocation and influence control flow. In browser contexts this class of bug is a frequent pathway to arbitrary code execution within the renderer or related process, often serving as the initial stage of a sandbox escape chain. Google internally rated this Medium severity despite the high CVSS score.
RemediationAI
Vendor-released patch: update Google Chrome to version 149.0.7827.53 or later on the Stable channel, as documented in the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Most managed Chrome deployments will receive this through the standard auto-update mechanism; verify that auto-update is not disabled by enterprise policy and force a relaunch to apply the new binary. For environments that cannot patch immediately, a targeted compensating control is to disable or restrict Chrome Remote Desktop usage via the RemoteAccessHostFirewallTraversal and related enterprise policies, or block the relevant Chromoting endpoints at the network egress - the trade-off is loss of remote desktop functionality for users who depend on it. Generic web-content mitigations like Site Isolation provide limited benefit here because the affected component is Chromoting rather than the renderer.
Same weakness CWE-416 – Use After Free
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34577
GHSA-x39c-xjvf-wfg8