dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-58729

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 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
Improper validation of specified type of input in Windows Local Session Manager (LSM) 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

Windows Local Session Manager (LSM) improper input validation allows an authenticated attacker to send specially crafted network requests that cause the service to fail, resulting in denial of service. The vulnerability stems from insufficient validation of a specific input type within the LSM component that handles local session management on Windows systems.

MitigationApply Microsoft security updates for CVE-2025-58729 when released. Until then, restrict network access to LSM-related ports using firewall rules and limit authorization to trusted administrators only.

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.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
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

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
    Run 'winver' or 'systeminfo' and note the OS Build number displayed (e.g., 10.0.19045.6456 for Windows 10 22h2)
    Affected if The installed build number is lower than the threshold for your Windows version: 1507 < 10.0.10240.21161, 1607 < 10.0.14393.8519, 1809 < 10.0.17763.7919, 21h2 < 10.0.19044.6456, 22h2 < 10.0.19045.6456, 11_22h2 < 10.0.22621.6060, 11_23h2 < 10.0.22631.6060, 11_24h2 < 10.0.26100.6899
  2. Identify Windows version branch
    Run 'winver' to determine if you are on Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 22h2, 23h2, 24h2
    Affected if The system runs any of the affected Windows versions listed and the build is below the corresponding threshold
  3. Verify LSM service presence
    Open Services console (services.msc) and locate 'Local Session Manager' service or run 'sc query' to enumerate services containing 'LSM' in the name
    Affected if The Local Session Manager service exists on the system (standard component for all affected Windows versions)
  4. Confirm network exposure of management interfaces
    Review Windows Firewall rules or run 'netsh advfirewall firewall show rule name=all' to identify any rules allowing remote access to session management features
    Affected if Unrestricted inbound rules exist that would allow remote network requests to reach LSM-related interfaces

The environment is affected if running any Windows 10 or Windows 11 version within the ranges listed and the installed build number falls below the specified threshold, with LSM accessible over the network.

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.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply Microsoft security updates for CVE-2025-58729 when released. Until then, restrict network access to LSM-related ports using firewall rules and limit authorization to trusted administrators only.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.21161 | Windows 10 1607: 10.0.14393.8519 | Windows 10 1809: 10.0.17763.7919 | Windows 10 21h2: 10.0.19044.6456 | Windows 10 22h2: 10.0.19045.6456 | Windows 11 22h2: 10.0.22621.6060 | Windows 11 23h2: 10.0.22631.6060 | Windows 11 24h2: 10.0.26100.6899

  1. 1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which affected version category applies to your system (Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, 24h2)
  3. 3. Apply the appropriate Windows Security Update that addresses CVE-2025-58729
  4. 4. Verify the update was successful by checking the Windows version matches or exceeds the fixed build number for your version
  5. 5. Restart the system if prompted to complete the update installation
Caveat Standard Windows update with no special configuration or migration requirements; apply via Windows Update or your organization's patch management

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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