CVE-2025-53722
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 · uneditedUncontrolled resource consumption in Windows Remote Desktop Services allows an unauthorized attacker to deny service 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 confidenceA denial of service vulnerability exists in Windows Remote Desktop Services where the service fails to properly control resource consumption when handling certain network requests. An unauthenticated remote attacker can send specially crafted requests to cause the RDS to consume excessive resources or become unresponsive, resulting in service availability loss.
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< 10.0.10240.21100< 10.0.14393.8330< 10.0.17763.7678< 10.0.19044.6216< 10.0.19045.6216< 10.0.22621.5768< 10.0.22631.5768< 10.0.26100.4851CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check Windows build versionOpen Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows build numberAffected if The displayed build number falls below any of these thresholds: Windows 10 1507 <10.0.10240.21100, 1607 <10.0.14393.8330, 1809 <10.0.17763.7678, 21h2 <10.0.19044.6216, 22h2 <10.0.19045.6216; Windows 11 22h2 <10.0.22621.5768, 23h2 <10.0.22631.5768, 24h2 <10.0.26100.4851
-
Confirm Remote Desktop Services are enabledOpen Services console (services.msc) and locate 'Remote Desktop Services' or run 'Get-Service TermService' in PowerShell to check if the Remote Desktop Service (TermService) is runningAffected if The TermService is running and listening on RDP port 3389, exposing the service to network requests
-
Check RDP listening status and network exposureRun 'netstat -an | findstr :3389' in Command Prompt to confirm the RDP port is in LISTENING state, and verify firewall rules allow incoming RDP connections with 'netsh advfirewall firewall show rule name=all | findstr /i "Remote Desktop"'Affected if Port 3389 is listening and accessible from the network (not blocked by firewall), making the system remotely exploitable
You are affected if your Windows build is below the thresholds listed AND Remote Desktop Services are enabled and exposed to network access.
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.10240.2110010.0.14393.833010.0.17763.7678
Apply Microsoft security patches for CVE-2025-53722 when available. As an interim measure, consider implementing network-level filtering, rate limiting on RD Gateway, or restricting RDP access to trusted IP ranges until patches can be deployed.
Apply Microsoft security update for CVE-2025-53722 to reach the minimum fixed build version for your Windows release
- Check current Windows version by running 'winver' or 'systeminfo' to identify which build is installed
- Open Settings > Windows Update > Check for updates, or use WSUS/SCCM for enterprise deployment
- Apply the relevant Microsoft security update for CVE-2025-53722 from Windows Update or the Microsoft Update Catalog (catalog.update.microsoft.com)
- Restart the system after applying the update
- Verify the update installed successfully by checking 'winver' to confirm the build number meets or exceeds the fixed version for your Windows release
- For Windows 10 1507 ensure build >= 10.0.10240.21100, for 1607 ensure >= 10.0.14393.8330, for 1809 ensure >= 10.0.17763.7678, for 21h2 ensure >= 10.0.19044.6216, for 22h2 ensure >= 10.0.19045.6216, for Windows 11 22h2 ensure >= 10.0.22621.5768, for 23h2 ensure >= 10.0.22631.5768, for 24h2 ensure >= 10.0.26100.4851
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53722 — 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-53722 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