dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-47653

HIGH · 8.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 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 remote attacker to achieve code execution by exploiting memory that is accessed after being freed. This is a memory corruption issue in the client software that can be triggered over a network connection.

MitigationApply vendor patches for the Remote Desktop Client when available; until then, restrict network exposure, disable RDP client usage on untrusted connections, 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
Windows 10 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

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. Locate the Remote Desktop Client executable
    Verify the mstsc.exe file exists at C:\Windows\System32\mstsc.exe
    Affected if The file does not exist (Remote Desktop Client may not be installed)
  2. Retrieve the mstsc.exe file version
    Open PowerShell and run: (Get-Item 'C:\Windows\System32\mstsc.exe').VersionInfo.FileVersion to get the version string, or right-click mstsc.exe, select Properties, and view the Details tab
    Affected if The command fails or the file cannot be accessed
  3. Identify your Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine your Windows build
    Affected if Unable to determine the Windows version or build number
  4. Compare installed version against affected ranges
    Match your Windows version to the appropriate affected range and compare your mstsc.exe version to the patched version threshold: Windows 10 1607 requires 10.0.14393.9234, Windows 10 1809 requires 10.0.17763.8880, Windows 10 21h2 requires 10.0.19044.7417, Windows 10 22h2 requires 10.0.19045.7417, Windows 11 23h2 requires 10.0.22631.7219, Windows 11 24h2 requires 10.0.26100.8655, Windows 11 25h2 requires 10.0.26200.8655, Windows 11 26h1 requires 10.0.28000.2269
    Affected if Your mstsc.exe version is lower than the patched version for your Windows build

Your environment is affected if the Remote Desktop Client (mstsc.exe) version is lower than the threshold for your specific Windows version and build.

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 10.0.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply vendor patches for the Remote Desktop Client when available; until then, restrict network exposure, disable RDP client usage on untrusted connections, and monitor for anomalous RDP activity.

Recommended fix High confidence

Windows 10/11 version-specific cumulative updates matching the fixed build numbers (10.0.14393.9234, 10.0.17763.8880, 10.0.19044.7417, 10.0.19045.7417, 10.0.22631.7219, 10.0.26100.8655, 10.0.26200.8655, or 10.0.28000.2269 depending on release)

  1. Identify the Windows version installed by running `winver` or checking System Information
  2. For Windows 10 1607: Upgrade to version 10.0.14393.9234 or later
  3. For Windows 10 1809: Upgrade to version 10.0.17763.8880 or later
  4. For Windows 10 21h2: Upgrade to version 10.0.19044.7417 or later
  5. For Windows 10 22h2: Upgrade to version 10.0.19045.7417 or later
  6. For Windows 11 23h2: Upgrade to version 10.0.22631.7219 or later
  7. For Windows 11 24h2: Upgrade to version 10.0.26100.8655 or later
  8. For Windows 11 25h2: Upgrade to version 10.0.26200.8655 or later
Caveat Standard Windows update risks apply - ensure backups and test in staging environment before broad deployment

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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