dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59204

MEDIUM · 5.5 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 →
57/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
Use of uninitialized resource in Windows Management Services allows an authorized attacker to disclose information 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 is a use-of-uninitialized-resource vulnerability in Windows Management Services. When a variable, memory buffer, or other resource is used before being properly initialized, it may contain residual data from previous operations. An authorized local attacker can exploit this to read sensitive information from uninitialized memory that gets returned or exposed through the service.

MitigationApply the vendor patch for CVE-2025-59204 when available. Until then, limit local access to trusted, authorized users only and monitor for anomalous access patterns to Windows Management Services.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Identify Windows version and build number
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell to obtain the exact build version (e.g., 10.0.17763.x)
    Affected if The displayed build number is lower than the fixed version for your specific Windows release (e.g., below 10.0.17763.7919 for Windows 10 1809/Server 2019, below 10.0.19044.6456 for Windows 10 21h2, etc.)
  2. Confirm Windows Management Services status
    Run 'Get-Service WinRM' in PowerShell to check if the Windows Remote Management service is installed and running
    Affected if The WinRM service is present and running, as this is the service component containing the vulnerable code
  3. Verify Server 2019 if applicable
    For Windows Server 2019 systems, run 'Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object CurrentBuild, DisplayVersion' to confirm the build
    Affected if The build number is below 10.0.17763.7919 on Windows Server 2019
  4. Check Windows 11 version range
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify if the system is Windows 11 22h2, 23h2, 24h2, or 25h2 and obtain the specific build
    Affected if The build is below 10.0.22621.6060 (22h2), below or equal to 10.0.22631.6060 (23h2), below 10.0.26100.6899 (24h2), or below 10.0.26200.6899 (25h2)

You are affected if your Windows version matches any of the listed affected products AND its build number falls below the corresponding fixed version threshold, with WinRM service enabled.

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 the vendor patch for CVE-2025-59204 when available. Until then, limit local access to trusted, authorized users only and monitor for anomalous access patterns to Windows Management Services.

Recommended fix High confidence

Install the appropriate monthly cumulative security update (KB) for your specific Windows version that includes the fix for CVE-2025-59204 - fixed builds: 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+), W

  1. Identify the installed Windows version and build number by running 'winver' or 'systeminfo'
  2. Open Settings > Windows Update > Check for updates
  3. Install all available cumulative security updates for your Windows version
  4. Alternatively, manually download and install the specific KB patch for your Windows version from the Microsoft Update Catalog
  5. Restart the system after installing the update
  6. Verify the update was installed successfully by checking the installed updates list or running 'winver' to confirm the build number matches or exceeds the fixed version
Caveat Standard cumulative security updates typically have minimal risk; ensure critical business applications are tested before deploying in production environments

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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