dbcve.org
Windows Server 2008Operating system · Microsoft

CVE-2025-32710

HIGH · 8.1 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.14393.8066 / 10.0.17763.7314 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Windows Remote Desktop Services 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 Windows Remote Desktop Services allows an unauthenticated attacker to achieve remote code execution by exploiting improper memory management in the RDS component. The vulnerability stems from the service accessing memory after it has been freed, which can be triggered via network-based attacks.

MitigationApply the relevant Microsoft security patches for Windows Remote Desktop Services as soon as they become available; in the interim, restrict network access to RDS endpoints via firewall rules or disable RDS if not required.

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 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8066
Windows Server 2019Operating system
Affected:< 10.0.17763.7314
Windows Server 2022Operating system
Affected:< 10.0.20348.3630
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1611
Windows Server 2025Operating system
Affected:< 10.0.26100.3981

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/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. Verify if Remote Desktop Services is enabled
    Open Services (services.msc) and check if 'Remote Desktop Services' or 'Remote Desktop Services (TermService)' is running, or run 'Get-Service TermService' in PowerShell
    Affected if RDS/TermService is running and the Windows version falls within the affected ranges below
  2. Check installed Windows Server version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows version and build number
    Affected if Version is Windows Server 2008 (any), 2012 (any), 2016 < 10.0.14393.8066, 2019 < 10.0.17763.7314, 2022 < 10.0.20348.3630, 2022 23h2 < 10.0.25398.1611, or 2025 < 10.0.26100.3981
  3. Confirm RDP network listening status
    Run 'netstat -an | findstr :3389' or check Windows Firewall rules for inbound RDP traffic (Remote Desktop)
    Affected if Port 3389 is listening and accepting connections from network sources
  4. Check for recent security updates related to Remote Desktop
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security patches
    Affected if No recent security updates for Remote Desktop Services are installed and the version is within affected ranges

If Remote Desktop Services is enabled and the Windows Server version is below the specified build numbers for each version, the environment is likely affected by this vulnerability.

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.8066 / 10.0.17763.7314 / 10.0.20348.3630 or later
Fixed in 10.0.14393.806610.0.17763.731410.0.20348.3630
Interim mitigation

Apply the relevant Microsoft security patches for Windows Remote Desktop Services as soon as they become available; in the interim, restrict network access to RDS endpoints via firewall rules or disable RDS if not required.

Recommended fix High confidence

Windows Server 2016: build 10.0.14393.8066 | Windows Server 2019: build 10.0.17763.7314 | Windows Server 2022: build 10.0.20348.3630 | Windows Server 2022 23h2: build 10.0.25398.1611 | Windows Server 2025: build 10.0.26100.3981

  1. Check current Windows Server version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify the applicable security update for CVE-2025-32710 from the Microsoft Security Update Guide (msrc.microsoft.com)
  3. Apply the relevant security update via Windows Update, Windows Server Update Services (WSUS), or by downloading from Microsoft Update Catalog
  4. Restart the server as required to complete the patch installation
  5. Verify the patch was successfully installed by checking Windows Update history or running 'systeminfo' to confirm the updated build number
Caveat Windows Server 2008 and 2012 are end-of-life and receive no further security updates; consider upgrading to a supported version

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

Fix this in Windows Server 2008 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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