dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-58726

HIGH · 7.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 →
81/100
Remediation priority · High
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 access control in Windows SMB Server allows an authorized attacker to elevate privileges 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

Improper access control in Windows SMB Server allows an authenticated attacker to elevate privileges over a network. The vulnerability stems from insufficient validation of access control checks within the SMB protocol implementation, enabling a user with basic network access to manipulate SMB sessions or shares to gain higher-privilege account access.

MitigationApply the Microsoft security update for this CVE to affected Windows systems and review SMB share permissions and user access controls to ensure no unauthorized privilege escalation paths remain.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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. Determine Windows build version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the full build number
    Affected if The build number falls within any of the vulnerable ranges: < 10.0.10240.21161 (1507), < 10.0.14393.8519 (1607), < 10.0.17763.7919 (1809), < 10.0.19044.6456 (21h2), < 10.0.19045.6456 (22h2), < 10.0.22621.6060 (Win11 22h2), <= 10.0.22631.6060 (Win11 23h2), or < 10.0.26100.6899 (Win11 24h2)
  2. Verify SMB Server is enabled
    Run 'Get-SmbServerConfiguration' in PowerShell or check Services for 'Server' service status (services.msc)
    Affected if SMB Server (SMB1 or SMB2/3) is enabled and the Windows version is vulnerable
  3. Check SMB listening status
    Run 'Get-NetTCPConnection -LocalPort 445' or 'netstat -an | findstr :445' to see if SMB is listening on network interfaces
    Affected if The system is listening on TCP port 445 and the Windows version is vulnerable

You are affected if your Windows build version is lower than the patched version for your specific Windows release AND SMB Server is enabled and listening on 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 the Microsoft security update for this CVE to affected Windows systems and review SMB share permissions and user access controls to ensure no unauthorized privilege escalation paths remain.

Recommended fix High confidence

Upgrade to: 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

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which version range your system falls into from the affected versions list
  3. Apply the appropriate Windows security update for your version through Windows Update, or download from Microsoft Update Catalog
  4. Alternatively, enable SMB signing if not already required (though this is a best practice, it may not fully mitigate this specific privilege escalation)
  5. After patching, verify the installed version matches or exceeds the fixed build number for your release
  6. Restart the system if required by the update
Caveat Standard Windows update risks - test critical applications before broad deployment; may require restart

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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