Skip to main content
CVE-2025-58718VulnerabilityPublished Updated

CVE-2025-58718: Microsoft Remote Desktop client for Windows Desktop · Use After Free

Affects Microsoft Remote Desktop client for Windows DesktopSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% 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:H/A:H/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Microsoft Remote Desktop client for Windows DesktopAffected
  • =1.2.0.0
Fixed in–

AI-suggested

Until an official patch is released by Microsoft, organizations should implement the following specific mitigations: 1) Restrict Remote Desktop client connections to trusted servers only and avoid connecting to unknown or untrusted hosts. 2) Employ network-level protections such as VPNs, firewalls, and IP whitelisting to limit exposure of Remote Desktop clients to the internet. 3) Enable multi-factor authentication (MFA) on Remote Desktop connections to reduce risk from compromised credentials. 4) Monitor network traffic and endpoint logs for unusual Remote Desktop activity or signs of exploitation attempts. 5) Educate users about the risks of connecting to untrusted Remote Desktop servers and encourage cautious behavior. 6) Use application whitelisting and endpoint detection and response (EDR) solutions to detect and block suspicious code execution. 7) Prepare for rapid deployment of patches once Microsoft releases an update by maintaining an up-to-date asset inventory and patch management process. 8) Consider temporarily disabling Remote Desktop client usage in high-risk environments if feasible.

Description

Use after free in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

References

Community reviews

Loading reviews…