dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-21313

MEDIUM · 6.5 CVSS v3.1 Published 2025-01-14
Fix available
A fix is available. Upgrade to 10.0.25398.1369 / 10.0.26100.2894 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Windows Security Account Manager (SAM) Denial of Service Vulnerability

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 Denial of Service vulnerability in the Windows Security Account Manager (SAM), the Windows component responsible for storing user account information and credentials. A successful exploit would allow an attacker to cause the SAM service to become unavailable, potentially locking users out of the system or disrupting authentication services.

MitigationApply the Microsoft security update for CVE-2025-21313 to all affected Windows systems. As a DoS vulnerability in a core authentication component, prioritize patching domain controllers and systems with elevated privileges.

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 24h2Operating system
Affected:< 10.0.26100.2894
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1369
Windows Server 2025Operating system
Affected:< 10.0.26100.2894

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

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

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

  1. Check Windows build version
    Open Command Prompt and run 'winver' to display the Windows version and build number, or run 'systeminfo | findstr /C:"OS Version"' to get detailed version information.
    Affected if The displayed build number is below 10.0.26100.2894 for Windows 11 24h2 or Windows Server 2025, or below 10.0.25398.1369 for Windows Server 2022 23h2.
  2. Identify Windows edition
    Run 'winver' or check System Properties to confirm whether the system is Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025.
    Affected if The system is running any of the three affected editions listed in the CVE.
  3. Compare against CVE version thresholds
    Match the identified Windows edition and build number against the affected version ranges: Windows 11 24h2 and Server 2025 require build 10.0.26100.2894 or higher; Windows Server 2022 23h2 requires build 10.0.25398.1369 or higher.
    Affected if The installed build number is lower than the required threshold for the detected Windows edition.

A system is affected if it is running Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025 with a build number below the respective threshold, as this indicates the SAM component is the vulnerable, unpatched version.

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.25398.1369 / 10.0.26100.2894 or later
Fixed in 10.0.25398.136910.0.26100.2894
Interim mitigation

Apply the Microsoft security update for CVE-2025-21313 to all affected Windows systems. As a DoS vulnerability in a core authentication component, prioritize patching domain controllers and systems with elevated privileges.

Recommended fix High confidence

Windows 11 24h2: Build 10.0.26100.2894 | Windows Server 2022 23h2: Build 10.0.25398.1369 | Windows Server 2025: Build 10.0.26100.2894

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Update: Settings > Update & Security > Windows Update
  3. Click 'Check for updates' and install all available security updates
  4. Alternatively, download the specific security update from Microsoft Catalog using KB ID (refer to MSRC for the specific KB for your Windows version)
  5. Restart the system after updates are installed
  6. Verify the version has been updated to one of the fixed builds: Windows 11 24h2 should be 10.0.26100.2894 or later, Windows Server 2022 23h2 should be 10.0.25398.1369 or later, Windows Server 2025 should be 10.0.26100.2894 or later
Caveat Standard Windows security updates typically have no breaking changes; however, test in staging if applicable

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21313 — 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-2025-21313 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