CVE-2025-32715: Microsoft Remote Desktop client for Windows Desktop · Out-of-bounds Read
Affects Microsoft Remote Desktop client for Windows DesktopSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
NuGetmicrosoft.remotedesktop.clientpkg:nuget/microsoft.remotedesktop.clientOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2025-32715, organizations should: 1) Monitor Microsoft security advisories closely and apply patches or updates as soon as they become available for the Remote Desktop client. 2) Restrict Remote Desktop client usage to trusted networks and endpoints, employing network segmentation and firewall rules to limit exposure. 3) Educate users to avoid connecting to untrusted or unknown Remote Desktop servers to reduce the risk of triggering the vulnerability. 4) Implement multi-factor authentication (MFA) for Remote Desktop access to reduce the impact of potential credential disclosure. 5) Use endpoint detection and response (EDR) tools to monitor for unusual Remote Desktop client behavior or suspicious network connections. 6) Consider deploying network-level protections such as VPNs or Remote Desktop Gateways to add layers of security. 7) Regularly audit Remote Desktop client versions in use across the organization to identify and remediate outdated or vulnerable installations. These steps go beyond generic advice by focusing on user behavior, network controls, and proactive patch management tailored to this specific vulnerability.
Description
Out-of-bounds read in Remote Desktop Client allows an unauthorized attacker to disclose information over a network.