dbcve.org
Remote Desktop ClientApplication · Microsoft

CVE-2026-32157

HIGH · 8.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 2.0.1070.0 / 10.0.14393.9060 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

A use-after-free vulnerability in the Remote Desktop Client enables an unauthenticated attacker to achieve remote code execution over a network by exploiting memory corruption through the RDP protocol.

MitigationApply vendor security updates for the Remote Desktop Client when released; until then, restrict RDP connections to trusted networks and hosts, and monitor for anomalous RDP activity.

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:< 2.0.1070.0
Windows 10 1607Operating system
Affected:< 10.0.14393.9060
Windows 10 1809Operating system
Affected:< 10.0.17763.8644
Windows 10 21h2Operating system
Affected:< 10.0.19044.7184
Windows 10 22h2Operating system
Affected:< 10.0.19045.7184
Windows 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246

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 Command Prompt or PowerShell and run: msrdc.exe /version or mstsc.exe /version. Alternatively, navigate to %SystemRoot%\System32\msrdc.exe or mstsc.exe, right-click, select Properties, and view the File Version on the Details tab.
    Affected if The displayed version is lower than 2.0.1070.0 or cannot be determined (older client installation).
  2. Check Windows version via systeminfo
    Run `systeminfo` in Command Prompt or `Get-ComputerInfo | Select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer` in PowerShell. Note the full Windows build number.
    Affected if The Windows build number is lower than the specified threshold for your Windows 10/11 version (10.0.14393.9060 for 1607, 10.0.17763.8644 for 1809, 10.0.19044.7184 for 21h2, 10.0.19045.7184 for 22h2, 10.0.22631.6936 for 23h2, 10.0.26100.8246 for 24h2, or 10.0.26200.8246 for 25h2).
  3. Check installed Windows updates
    Run `Get-HotFix | Where-Object {$_.Description -eq 'Security Update'} | Sort-Object InstalledOn -Descending | Select-Object -First 10` in PowerShell, or open Settings > Windows Update > Update history to view recent security patches.
    Affected if No recent security updates related to Remote Desktop Client or Windows RDP have been installed, or the system has not been patched to the required build numbers.

You are affected if the Remote Desktop Client version is below 2.0.1070.0 OR the Windows build number is below the threshold for your specific Windows version, indicating an unpatched system vulnerable to the use-after-free flaw.

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 2.0.1070.0 / 10.0.14393.9060 / 10.0.17763.8644 or later
Fixed in 2.0.1070.010.0.14393.906010.0.17763.8644
Interim mitigation

Apply vendor security updates for the Remote Desktop Client when released; until then, restrict RDP connections to trusted networks and hosts, and monitor for anomalous RDP activity.

Recommended fix High confidence

Apply the Microsoft security update that addresses CVE-2026-32157 (monthly cumulative update containing the fix for this Remote Desktop Client use-after-free vulnerability)

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually download the specific security update from Microsoft Update Catalog for your Windows version
  4. Ensure Remote Desktop Client is updated as part of the cumulative security patch
  5. Restart the system if prompted to complete the installation
  6. Verify the installed update by running 'winver' to confirm the build number meets or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply - ensure critical data is backed up before applying updates

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

Fix this in Remote Desktop Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32157 — 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-2026-32157 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