dbcve.org
Windows Server 2016Operating system · Microsoft

CVE-2026-47654

HIGH · 7.5 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 →
82/100
Remediation priority · High
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 (UAF) vulnerability in Remote Desktop Client allows an attacker to execute arbitrary code by manipulating memory after it has been freed, potentially through malicious RDP sessions or man-in-the-middle attacks.

MitigationApply vendor patches for the Remote Desktop Client; if no patch available, restrict network exposure and monitor for suspicious 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 Server 2016Operating system
Affected:< 10.0.14393.9234
Windows Server 2019Operating system
Affected:< 10.0.17763.8880
Windows Server 2022Operating system
Affected:< 10.0.20348.5256
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 Windows Server version
    Run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to identify the installed Windows Server version
    Affected if The version falls below 10.0.14393.9234 (Server 2016), 10.0.17763.8880 (Server 2019), 10.0.20348.5256 (Server 2022), or 10.0.26100.32995 (Server 2025)
  2. Verify Remote Desktop Client is present
    Check if mstsc.exe exists in C:\Windows\System32\ or run `Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\mstsc.exe" -ErrorAction SilentlyContinue`
    Affected if The Remote Desktop Client executable (mstsc.exe) is installed on the system
  3. Confirm RDP Client service status
    Run `Get-Service -Name UmRdpService -ErrorAction SilentlyContinue` or check Remote Desktop Services in services.msc
    Affected if The Remote Desktop Services (or Remote Desktop UserDIagnostics) service is running or enabled, indicating active RDP client functionality

A system is affected if it runs an unpatched Windows Server version within the affected ranges AND has the Remote Desktop Client component installed and enabled for use.

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.20348.5256 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.20348.5256
Interim mitigation

Apply vendor patches for the Remote Desktop Client; if no patch available, restrict network exposure and monitor for suspicious RDP activity.

Recommended fix High confidence

Apply Microsoft security updates for CVE-2026-47654 to reach the fixed build numbers (10.0.14393.9234 or higher for Server 2016, 10.0.17763.8880 or higher for Server 2019, 10.0.20348.5256 or higher for Server 2022, 10.0.26100.32995 or higher for Server 2025)

  1. Identify the Windows Server version currently installed by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Settings and navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually install the specific Microsoft security update from the Microsoft Update Catalog for your Windows Server version: KB5055529 (Server 2016), KB5055518 (Server 2019), KB5055520 (Server 2022), KB5055517 (Server 2025)
  5. Restart the server after applying updates
  6. Verify the installed version meets or exceeds the fixed threshold: Server 2016 → 10.0.14393.9234, Server 2019 → 10.0.17763.8880, Server 2022 → 10.0.20348.5256, Server 2025 → 10.0.26100.32995
Caveat Standard Windows update applies—review test environment results before broad deployment; ensure backups and rollback plans are in place

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

Fix this in Windows Server 2016 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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