CVE-2025-58737
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 · uneditedUse after free in Windows Remote Desktop allows an unauthorized attacker to execute code locally.
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 confidenceA use-after-free vulnerability in Windows Remote Desktop allows an unauthorized local attacker to execute arbitrary code. The vulnerability stems from improper memory management in the Remote Desktop component, where memory is accessed after being freed, leading to potential code execution.
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= r2<= 10.0.14393.8519< 10.0.17763.7919< 10.0.20348.4294< 10.0.25398.1913<= 10.0.26100.6899CVSS 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
- Local
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows Server versionRun 'winver' from command prompt, or use 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"', or query registry: reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuildAffected if The displayed version falls within or below these affected ranges: Server 2012 R2 (any), Server 2016 <= 10.0.14393.8519, Server 2019 < 10.0.17763.7919, Server 2022 < 10.0.20348.4294, Server 2022 23h2 < 10.0.25398.1913, Server 2025 <= 10.0.26100.6899
-
Verify Remote Desktop is enabledCheck registry key: reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections - value 0 means enabled, 1 means disabled. Or check via System Properties (right-click This PC > Properties > Remote settings)Affected if The fDenyTSConnections value is 0 (Remote Desktop is enabled)
-
Confirm Remote Desktop service statusOpen Services console (services.msc) and check 'Remote Desktop Services' service status, or run: sc query TermServiceAffected if The Remote Desktop service (TermService) is running
You are affected if your Windows Server version is within the affected ranges listed AND Remote Desktop is enabled and running on your system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.17763.791910.0.20348.429410.0.25398.1913
Apply the relevant Microsoft security patch for this vulnerability. Until the patch is available, restrict Remote Desktop access to trusted users and monitor for indicators of compromise.
Windows Server 2016: build > 10.0.14393.8519 | Windows Server 2019: build >= 10.0.17763.7919 | Windows Server 2022: build >= 10.0.20348.4294 | Windows Server 2022 23h2: build >= 10.0.25398.1913 | Windows Server 2025: build > 10.0.26100.6899
- Open Windows Update on the affected server
- Check for and install the latest Windows security updates
- Verify the Remote Desktop services have been updated to the fixed versions
- Restart the server if prompted by the update installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58737 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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