dbcve.org
Windows 11 22h2Operating system · Microsoft

CVE-2025-59284

MEDIUM · 5.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.22621.6060 / 10.0.22631.6060 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Exposure of sensitive information to an unauthorized actor in Windows NTLM allows an unauthorized attacker to perform spoofing 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 vulnerability in Windows NTLM (NT LAN Manager) authentication allows an unauthorized local attacker to access sensitive information that can then be used to perform spoofing attacks. The issue stems from improper exposure of NTLM credentials or authentication artifacts that should remain protected, enabling an attacker with local access to impersonate other users or systems.

MitigationApply the relevant Windows security update to patch the NTLM vulnerability. Consider disabling NTLM authentication where possible and enforcing Kerberos authentication, or implementing additional controls like SMB signing and NTLM blocking policies.

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 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2025Operating system
Affected:< 10.0.26100.6899

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"Version" /C:"Build"' to get the exact build number
    Affected if The build number is lower than the affected versions: 22621.6060 for 22h2, 22631.6060 for 23h2, 26100.6899 for 24h2/Server 2025, or 26200.6899 for 25h2
  2. Verify NTLM authentication is enabled
    Check registry key 'HKLM\SYSTEM\CurrentControlSet\Control\Lsa\LMCompatibilityLevel' or run 'gpresult /r | findstr NTLM' to see if NTLM is permitted
    Affected if NTLM authentication is allowed (LMCompatibilityLevel is 0-3, or NTLM is not explicitly blocked in Group Policy)
  3. Review NTLM security event logs
    Open Event Viewer, navigate to Security logs, and filter for Event ID 4624 (successful logon) with Logon Type 3, or Event ID 4656 for NTLM credential usage
    Affected if There are NTLM authentication events in the logs indicating NTLM is being used in the environment
  4. Check for NTLM credential caching
    Run 'reg query "HKLM\SECURITY\Cache"' to examine cached credentials, or check 'net use' for active SMB sessions using NTLM
    Affected if Cached credentials exist or active NTLM-authenticated sessions are present

You are affected if your Windows build version is lower than the fixed versions AND NTLM authentication is enabled in your environment.

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.22621.6060 / 10.0.22631.6060 / 10.0.26100.6899 or later
Fixed in 10.0.22621.606010.0.22631.606010.0.26100.6899
Interim mitigation

Apply the relevant Windows security update to patch the NTLM vulnerability. Consider disabling NTLM authentication where possible and enforcing Kerberos authentication, or implementing additional controls like SMB signing and NTLM blocking policies.

Recommended fix High confidence
  1. Open Settings > Windows Update on the affected Windows machine
  2. Click 'Check for updates' to retrieve the latest available updates
  3. Install all cumulative security updates for your Windows version
  4. After installation, restart the computer when prompted
  5. Verify the installed update by checking Windows Update history - the KB number for this month's security update should be present

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

Fix this in Windows 11 22h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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