dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-32724

HIGH · 7.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Uncontrolled resource consumption in Windows Local Security Authority Subsystem Service (LSASS) 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 confidence

A denial-of-service vulnerability exists in Windows LSASS (Local Security Authority Subsystem Service) where an unauthorized remote attacker can cause uncontrolled resource consumption, leading to service failure and potential system-wide authentication disruptions.

MitigationApply the relevant Microsoft security update for this vulnerability across all affected Windows systems. Given LSASS criticality to Windows authentication, test patches in a staging environment before production deployment.

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 10 1507Operating system
Affected:< 10.0.10240.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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
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 checks

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

  1. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the full version number, then compare the Build number to the affected ranges provided
    Affected if The Build number falls below any of these thresholds: 10240.21034, 14393.8148, 17763.7434, 19044.5965, 19045.5965, 22621.5472, 22631.5472, 26100.4270
  2. Confirm LSASS service is running
    Open Services (services.msc) and verify the 'Local Security Authority Subsystem Service' (LSASS) status is Running, or run 'sc query lsass'
    Affected if LSASS is running (this is the default and required state; the vulnerability exists in the running service)
  3. Check for installed security updates
    Run 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"}' or view the Windows Update history in Settings > Windows Update > Update history to look for recent security patches
    Affected if No security update addressing this CVE is listed in the update history and the Windows version is within an affected build range

A system is affected if it runs a Windows version with a Build number lower than the thresholds listed AND lacks the corresponding security update for CVE-2025-32724.

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.10240.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply the relevant Microsoft security update for this vulnerability across all affected Windows systems. Given LSASS criticality to Windows authentication, test patches in a staging environment before production deployment.

Recommended fix High confidence

Windows 10 1507: Build 10.0.10240.21034 | Windows 10 1607: Build 10.0.14393.8148 | Windows 10 1809: Build 10.0.17763.7434 | Windows 10 21h2: Build 10.0.19044.5965 | Windows 10 22h2: Build 10.0.19045.5965 | Windows 11 22h2: Build 10.0.22621.5472 | Windows 11 23h2: Build 10.0.22631.5472 | Windows 11 2

  1. 1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which version category applies (Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, 24h2)
  3. 3. Open Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest security updates
  5. 5. Alternatively, manually download the specific KB update from the Microsoft Update Catalog for your Windows version
  6. 6. After installation, restart the system to apply the LSASS patch
  7. 7. Verify the update was applied by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard Windows security update risks - ensure backups exist and testing on non-critical systems first; LSASS restarts may briefly affect authentication services

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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