CVE-2025-59502
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 Procedure Call 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 confidenceUncontrolled resource consumption in Windows Remote Procedure Call (RPC) allows an unauthenticated remote attacker to cause denial of service by exhausting system resources over a network.
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.17763.7792< 10.0.19044.6332< 10.0.19045.6332< 10.0.22621.5909< 10.0.22631.5909< 10.0.26100.6508< 10.0.17763.7792< 10.0.20348.4106CVSS 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 installed Windows build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number, then compare it against the affected version thresholds: Windows 10 1809/Server 2019 needs 10.0.17763.7792 or higher; Windows 10 21h2 needs 10.0.19044.6332 or higher; Windows 10 22h2 needs 10.0.19045.6332 or higher; Windows 11 22h2 needs 10.0.22621.5909 or higher; Windows 11 23h2 needs 10.0.22631.5909 or higher; Windows 11 24h2 needs 10.0.26100.6508 or higher; Windows Server 2022 needs 10.0.20348.4106 or higherAffected if The installed build number is lower than the corresponding threshold for your Windows version
-
Verify RPC service exposureCheck if the RPC Endpoint Mapper (port 135) and RPC dynamic ports are accessible from untrusted networks by running 'netsh advfirewall firewall show rule name=all' or using a port scanner from an external system targeting ports 135, 49152-49155, and 49157-49172Affected if RPC ports (135 and dynamic range) are open to untrusted or internet-facing network interfaces
-
Confirm RPC service is runningRun 'Get-Service RpcSs' or 'sc query RpcSs' to verify the RPC Endpoint Mapper service statusAffected if The RPC service is running and network-accessible
-
Review event logs for DoS indicatorsCheck Windows Event Viewer under Application and Services Logs > System for Event ID 4227 or 4228 indicating TCP/IP port exhaustion, or Event ID 7036 for service failure eventsAffected if System event logs show repeated RPC-related resource exhaustion or service crashes
You are affected if your Windows build is below the patched threshold AND RPC services are exposed to untrusted network segments, as an unauthenticated remote attacker could exploit this to cause denial of service.
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.779210.0.19044.633210.0.19045.6332
Apply the relevant Microsoft Windows security update to patch the RPC service; implement network-level rate limiting or firewall rules to restrict RPC traffic from untrusted sources as a temporary mitigation.
Windows 10 1809: 10.0.17763.7792 or later | Windows 10 21h2: 10.0.19044.6332 or later | Windows 10 22h2: 10.0.19045.6332 or later | Windows 11 22h2: 10.0.22621.5909 or later | Windows 11 23h2: 10.0.22631.5909 or later | Windows 11 24h2: 10.0.26100.6508 or later | Windows Server 2019: 10.0.17763.7792
- Identify the current Windows version and build number by running 'winver' or 'systeminfo'
- Open Windows Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the latest security updates
- Alternatively, manually download and install the appropriate cumulative security update for your Windows version from the Microsoft Update Catalog
- Restart the system after applying the update
- Verify the update was successful by checking the installed updates in Control Panel > Programs > Programs and Features > View installed updates
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-59502 — 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-59502 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