dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-53716

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.17763.7678 / 10.0.19044.6216 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
Null pointer dereference in Windows Local Security Authority Subsystem Service (LSASS) allows an authorized 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 null pointer dereference vulnerability in Windows Local Security Authority Subsystem Service (LSASS) can be exploited by an authorized network attacker to cause a denial of service, potentially crashing the LSASS process and disrupting authentication services.

MitigationApply Microsoft security updates for Windows when released; restrict network access to LSASS to authorized users only to reduce attack surface.

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 1809Operating system
Affected:< 10.0.17763.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851
Windows Server 2019Operating system
Affected:< 10.0.17763.7678
Windows Server 2022Operating system
Affected:< 10.0.20348.3989

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 number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /C:"Build"' to obtain the full OS build version.
    Affected if The build number is lower than any of these thresholds: 17763.7678 (Win 10 1809/Server 2019), 19044.6216 (Win 10 21h2), 19045.6216 (Win 10 22h2), 22621.5768 (Win 11 22h2), 22631.5768 (Win 11 23h2), 26100.4851 (Win 11 24h2), or 20348.3989 (Server 2022).
  2. Confirm exact Windows edition
    Run 'systeminfo' or 'winver' to verify whether the system is Windows 10, Windows 11, or Windows Server and the specific release (such as 1809, 21h2, 22h2, 23h2, 24h2, Server 2019, or Server 2022).
    Affected if The edition matches one of the affected products listed but the build number is below the corresponding threshold.
  3. Verify LSASS service status
    Open Services console (services.msc) or run 'sc query lsass' to confirm the Local Security Authority Subsystem Service is running.
    Affected if The LSASS service is running and the Windows version/build falls within the affected ranges.

A system is affected if it runs any of the listed Windows versions with a build number lower than the specified threshold for that release, and the LSASS service is active.

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.17763.7678 / 10.0.19044.6216 / 10.0.19045.6216 or later
Fixed in 10.0.17763.767810.0.19044.621610.0.19045.6216
Interim mitigation

Apply Microsoft security updates for Windows when released; restrict network access to LSASS to authorized users only to reduce attack surface.

Recommended fix High confidence

Apply Microsoft security updates for CVE-2025-53716 - the fixed versions are: Windows 10 1809: 10.0.17763.7678, Windows 10 21h2: 10.0.19044.6216, Windows 10 22h2: 10.0.19045.6216, Windows 11 22h2: 10.0.22621.5768, Windows 11 23h2: 10.0.22631.5768, Windows 11 24h2: 10.0.26100.4851, Windows Server 201

  1. Identify the Windows version and build number on affected systems using 'winver' or 'systeminfo'
  2. Review Microsoft Security Response Center (msrc.microsoft.com) for the specific security bulletin associated with CVE-2025-53716
  3. Apply the latest Windows security update for the respective build version via Windows Update, WSUS, or manual download from Microsoft Update Catalog
  4. For managed environments, deploy the patch through organizational patch management tools
  5. Verify the patch was applied successfully by checking the LSASS version or build number post-update
  6. Restart the system if required by the security update
  7. Confirm the vulnerability is remediated by verifying the updated build number meets or exceeds the fixed version for your Windows edition

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

Fix this in Windows 10 1809 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-2025-53716 — 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-53716 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