dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59193

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Management Services allows an authorized attacker to elevate privileges 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

CVE-2025-59193 is a race condition vulnerability in Windows Management Services where improper synchronization of shared resources allows an authorized attacker to elevate privileges locally. The vulnerability stems from concurrent execution issues that can be exploited to gain higher-level access.

MitigationApply Microsoft security updates for Windows Management Services promptly; ensure affected systems are patched. Follow least-privilege principles and limit local access 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.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
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2019Operating system
Affected:< 10.0.17763.7919

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

CVSS:3.1/AV:L/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. Identify Windows version and build number
    Run 'winver' from command prompt or execute 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell to obtain the exact version and build
    Affected if The displayed build number falls below the affected threshold for your specific Windows edition (e.g., below 10.0.17763.7919 for Windows 10 1809 or Windows Server 2019)
  2. Confirm Windows Management Services component presence
    Open Services console (services.msc) or run 'Get-Service -Name WinMgmt' in PowerShell to verify the Windows Management Instrumentation service is installed and running
    Affected if The Windows Management Instrumentation (WMI) service exists on the system - this is the vulnerable component
  3. Verify build number via systeminfo
    Run 'systeminfo' from command prompt and examine the 'OS Version' field to obtain the precise build number for version comparison
    Affected if The reported build number is lower than the minimum fixed build for your Windows release (e.g., < 10.0.19045.6456 for Windows 10 22h2)

You are affected if your system runs any of the listed Windows versions with a build number lower than the corresponding fix threshold and has Windows Management Services present.

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.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply Microsoft security updates for Windows Management Services promptly; ensure affected systems are patched. Follow least-privilege principles and limit local access to reduce attack surface.

Recommended fix High confidence

Install the Microsoft security update containing CVE-2025-59193; specific build numbers: Windows 10 1809/Server 2019 to 10.0.17763.7919, Windows 10 21h2 to 10.0.19044.6456, Windows 10 22h2 to 10.0.19045.6456, Windows 11 22h2 to 10.0.22621.6060, Windows 11 23h2 to 10.0.22631.6061 or later, Windows 11

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest Microsoft security patches
  3. Ensure the patch KB5055523 (or subsequent security update containing CVE-2025-59193) is installed
  4. Restart the system to complete the patch installation
  5. Verify the installed Windows version matches or exceeds the fixed version for your build (e.g., 10.0.17763.7919 for Windows 10 1809/Server 2019, 10.0.19045.6456 for Windows 10 22h2, etc.)
Caveat Standard Windows security patch; no expected breaking changes for this privilege escalation fix

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-59193 — 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-59193 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