CVE-2026-44806
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 · uneditedMissing release of memory after effective lifetime in Windows Cryptographic Services allows an unauthorized attacker to deny service over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
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 memory leak vulnerability exists in Windows Cryptographic Services where memory is not released after effective lifetime. An unauthenticated remote attacker can exploit this to cause a denial of service by exhausting available memory through repeated requests to the cryptographic services.
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.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2269all versions= r2CVSS 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 versionRun 'winver' or 'systeminfo' to determine your installed Windows version and build numberAffected if Your Windows version and build number fall below the following thresholds: Windows 10 1607 < 10.0.14393.9339, Windows 10 1809 < 10.0.17763.9020, Windows 10 21h2 < 10.0.19044.7548, Windows 10 22h2 < 10.0.19045.7548, Windows 11 24h2 < 10.0.26100.8875, Windows 11 25h2 < 10.0.26200.8875, Windows 11 26h1
-
Verify Cryptographic Services are runningOpen Services (services.msc) and check for 'Cryptographic Services' service status, or run 'Get-Service CryptSvc' in PowerShellAffected if The Cryptographic Services service is running and your Windows version is in the affected list
-
Monitor for memory leaks in cryptographic processesOpen Task Manager, locate 'Cryptographic Services' (cryptsvc.exe) or related processes, and observe memory usage over time; use 'Get-Process cryptsvc' in PowerShell to check WorkingSet64 memory values repeatedlyAffected if Cryptographic service processes show continuously increasing memory consumption without stabilization or release over time
You are affected if your Windows version is in the affected version list AND the Cryptographic Services are running, particularly if you observe abnormally high or growing memory usage in cryptsvc.exe.
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.14393.933910.0.17763.902010.0.19044.7548
Apply the appropriate Microsoft security patch for Windows Cryptographic Services. Prioritize patching systems exposed to network attack vectors and monitor for anomalous memory consumption patterns.
Windows 10 1607: 10.0.14393.9339+ | Windows 10 1809: 10.0.17763.9020+ | Windows 10 21h2: 10.0.19044.7548+ | Windows 10 22h2: 10.0.19045.7548+ | Windows 11 24h2: 10.0.26100.8875+ | Windows 11 25h2: 10.0.26200.8875+ | Windows 11 26h1: 10.0.28000.2269+ | Windows Server 2012 R2: migrate to supported Ser
- Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Identify the specific Windows version and build number from the affected list
- For Windows 10 versions: Apply Windows Updates to install theKB patch for this CVE, which will upgrade the build to the fixed version (e.g., 10.0.14393.9339 or higher for 1607)
- For Windows 11 versions: Apply Windows Updates to install theKB patch, upgrading to the fixed build (e.g., 10.0.26100.8875 or higher for 24h2)
- For Windows Server 2012 R2: This version is end-of-life with no fix available; migrate to a supported Windows Server version (2016, 2019, 2022, or 2025)
- After patching, verify the fix by checking the Windows build number matches or exceeds the fixed versions listed
- Restart the system if required by the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44806 — 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-2026-44806 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