dbcve.org
Remote Desktop ClientApplication · Microsoft

CVE-2025-58718

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 1.2.6599 / 2.0.706.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Use-after-free vulnerability in Remote Desktop Client allows an unauthenticated attacker to achieve remote code execution by exploiting improper memory management. The attacker would need to have the victim connect to a malicious RDP server or man-in-the-middle an RDP connection.

MitigationApply vendor security patches when released; until then, restrict RDP connections to trusted servers only and consider network segmentation to limit exposure to malicious RDP servers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Remote Desktop ClientApplication
Affected:< 1.2.6599
Windows AppApplication
Affected:< 2.0.706.0
Windows 10 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Remote Desktop Client version
    Open Microsoft Remote Desktop Client, go to Settings (gear icon), then About or Help menu to view the version number. Alternatively, check Programs and Features or the app's properties in %LOCALAPPDATA%\Microsoft\RemoteDesktopClient
    Affected if Version is below 1.2.6599
  2. Check Microsoft Windows App version
    Open Microsoft Store, go to Library > My apps, find Microsoft Windows App and check the version. Or right-click the app in Start menu and select App info to view version
    Affected if Version is below 2.0.706.0
  3. Check Windows 10 version
    Run winver from Start menu search or type 'systeminfo' in Command Prompt to see the OS Build number under 'OS Version'
    Affected if Build number is below 21161 (1507), 8519 (1607), 7919 (1809), 6456 (21h2/22h2)
  4. Check Windows 11 version
    Run winver or type systeminfo in Command Prompt to view the OS Build number under 'OS Version'
    Affected if Build number is below 22621.6060 for Windows 11 22h2

Your environment is affected if you run any Remote Desktop Client below 1.2.6599, Microsoft Windows App below 2.0.706.0, or a Windows version with build number below the thresholds listed for your specific Windows release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.6599 / 2.0.706.0 / 10.0.10240.21161 or later
Fixed in 1.2.65992.0.706.010.0.10240.21161
Interim mitigation

Apply vendor security patches when released; until then, restrict RDP connections to trusted servers only and consider network segmentation to limit exposure to malicious RDP servers.

Recommended fix High confidence

Remote Desktop Client >= 1.2.6599, Windows App >= 2.0.706.0, Windows 10 1507 >= 10.0.10240.21161, Windows 10 1607 >= 10.0.14393.8519, Windows 10 1809 >= 10.0.17763.7919, Windows 10 21h2 >= 10.0.19044.6456, Windows 10 22h2 >= 10.0.19045.6456, Windows 11 22h2 >= 10.0.22621.6060

  1. 1. Identify the affected Microsoft product in your environment (Remote Desktop Client, Windows App, or specific Windows 10/11 version)
  2. 2. For Remote Desktop Client: Update to version 1.2.6599 or later via Microsoft Store or Microsoft official download
  3. 3. For Windows App: Update to version 2.0.706.0 or later via Microsoft Store
  4. 4. For Windows 10/11 systems: Run Windows Update to receive the security patch for your specific Windows version
  5. 5. Alternatively, manually install the corresponding KB (Knowledge Base) patch from Microsoft Update Catalog for your Windows version
  6. 6. Restart the affected systems after applying the updates
  7. 7. Verify the update was successful by checking the version number matches or exceeds the fixed versions listed
Caveat Standard Windows update process with minimal risk; ensure backups of critical data before applying patches

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Remote Desktop Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58718 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-58718 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data