dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-44810

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.20348.5256 / 10.0.22631.7219 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Improper authentication in Windows Cryptographic Services allows an unauthorized attacker to elevate privileges 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 confidence

This is a local privilege escalation vulnerability in Windows Cryptographic Services. An unauthenticated attacker with local access can bypass authentication mechanisms in the cryptographic services subsystem to elevate their privileges from a standard user to higher-level privileges (potentially SYSTEM).

MitigationApply Microsoft security updates for Windows Cryptographic Services once released. Prioritize patching domain controllers and systems handling sensitive cryptographic operations.

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
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2022Operating system
Affected:< 10.0.20348.5256
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full build number
    Affected if The build number falls below the fixed versions: 10.0.22631.7219 (23h2), 10.0.26100.8655 (24h2), 10.0.26200.8655 (25h2), 10.0.28000.2269 (26h1), 10.0.20348.5256 (Server 2022), or 10.0.26100.32995 (Server 2025)
  2. Verify Cryptographic Service status
    Open Services console (services.msc) or run 'Get-Service CryptSvc' in PowerShell to check if the Windows Cryptographic Services service exists and is running
    Affected if The CryptSvc service is present and running on an affected Windows version
  3. Check service configuration
    Run 'sc qc CryptSvc' in Command Prompt or 'Get-Service CryptSvc | Select-Object -Property Name, StartType, Status' in PowerShell to view the service startup type and status
    Affected if The service is set to Automatic or Manual start on an unpatched system
  4. Review system architecture
    Run 'systeminfo' in Command Prompt and note the OS Name and Version fields to confirm the exact Windows edition and version
    Affected if The system runs any of the affected Windows 11 versions (23h2, 24h2, 25h2, 26h1) or Windows Server 2022/2025 with build numbers below the fixed thresholds

A system is affected if it runs any of the listed Windows 11 or Windows Server versions with a build number lower than the corresponding fixed version, and the Cryptographic Services component is accessible locally.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.20348.5256 / 10.0.22631.7219 / 10.0.26100.8655 or later
Fixed in 10.0.20348.525610.0.22631.721910.0.26100.8655
Interim mitigation

Apply Microsoft security updates for Windows Cryptographic Services once released. Prioritize patching domain controllers and systems handling sensitive cryptographic operations.

Recommended fix High confidence

Upgrade to the latest Windows security update containing build 10.0.22631.7219 or higher for Windows 11 23h2; 10.0.26100.8655 or higher for Windows 11 24h2; 10.0.26200.8655 or higher for Windows 11 25h2; 10.0.28000.2269 or higher for Windows 11 26h1; 10.0.20348.5256 or higher for Windows Server 2022

  1. Identify the current Windows build version by running 'winver' or 'systeminfo' in command prompt
  2. Determine which Windows version and build is currently installed (e.g., Windows 11 23h2, Windows Server 2022, etc.)
  3. Navigate to Windows Update via Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to download and install the latest security updates
  5. Alternatively, manually download the appropriate security update from the Microsoft Update Catalog (catalog.update.microsoft.com) matching your Windows version and architecture
  6. Restart the system after updates are installed
  7. Verify the build number matches or exceeds the fixed version: Windows 11 23h2 should be 10.0.22631.7219+, Windows 11 24h2 should be 10.0.26100.8655+, Windows 11 25h2 should be 10.0.26200.8655+, Windows 11 26h1 should be 10.0.28000.2269+, Windows Server 2022 should be 10.0.20348.5256+, Windows Server 2025 should be 10.0.26100.32995+
Caveat Standard Windows update risks apply - ensure backups of critical data and compatibility testing for line-of-business applications before deploying broadly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44810 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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