CVE-2025-26641
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 Cryptographic 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 confidenceThis is a denial-of-service vulnerability in Windows Cryptographic Services where an unauthenticated remote attacker can cause uncontrolled resource consumption, leading to service disruption 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.10240.20978< 10.0.14393.7969< 10.0.17763.7136< 10.0.19044.5737< 10.0.19045.5737< 10.0.22621.5189< 10.0.22631.5189< 10.0.26100.3775CVSS 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 versionOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact build numberAffected if The build number is lower than the fixed version for your Windows 10 or 11 release (e.g., below 10.0.10240.20978 for 1507, below 10.0.22621.5189 for Win11 22h2)
-
Verify Cryptographic Service statusOpen Services (services.msc) and locate 'Cryptographic Services' or run 'Get-Service CryptSvc' in PowerShellAffected if The service is running (the vulnerability exists in this service regardless of network exposure)
-
Check network listening statusRun 'netstat -an | findstr "445\|139\|3389"' or use PowerShell 'Get-NetTCPConnection -State Listen' to see which ports are listeningAffected if The system has network services enabled (the DOS can be triggered remotely over the network)
-
Confirm domain controller role if applicableRun 'netdom query /domain:%USERDOMAIN% DC' or check Server Manager for Active Directory Domain Services roleAffected if The machine is a domain controller and the cryptographic services are exposed to network (remote unauthenticated attackers can target this service)
You are affected if your Windows build is below the fixed version AND the Cryptographic Services are running and network-accessible, enabling remote unauthenticated attackers to cause resource exhaustion.
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.2097810.0.14393.796910.0.17763.7136
Apply the Microsoft security update for CVE-2025-26641 through Windows Update or your organization's patch management system to address the uncontrolled resource consumption in Windows Cryptographic Services.
Apply March 2025 Windows security update (KB) matching your Windows 10/11 branch version, upgrading to minimum build: 10.0.10240.20978 (1507), 10.0.14393.7969 (1607), 10.0.17763.7136 (1809), 10.0.19044.5737 (21h2), 10.0.19045.5737 (22h2), 10.0.22621.5189 (Win11 22h2), 10.0.22631.5189 (Win11 23h2), o
- Identify the current Windows version and build number (winver or systeminfo)
- Compare the installed build against the fixed versions for your Windows release branch
- Obtain the corresponding security update from catalog.update.microsoft.com or via Windows Update
- Apply the security update (may require KB number matching your Windows version)
- Restart the system as prompted to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26641 — 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-26641 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