dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 14 Nov 2025.
Windows Server 2012Operating system · Microsoft

CVE-2025-59287

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.14393.8524 / 10.0.17763.7922 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges 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
Deserialization of untrusted data in Windows Server Update Service allows an unauthorized attacker to execute code 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

A deserialization vulnerability exists in Windows Server Update Service (WSUS) where untrusted data is deserialized without proper validation, allowing an unauthenticated remote attacker to execute arbitrary code over the network.

MitigationApply Microsoft security patches for CVE-2025-59287 immediately; restrict network access to WSUS servers and ensure they are not directly exposed to the internet until patched.

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 Server 2012Operating system
Affected:all versions= r2
Windows Server 2016Operating system
Affected:< 10.0.14393.8524
Windows Server 2019Operating system
Affected:< 10.0.17763.7922
Windows Server 2022Operating system
Affected:< 10.0.20348.4297
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1916
Windows Server 2025Operating system
Affected:< 10.0.26100.6905

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Windows Server version
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows Server build number
    Affected if The version is below 10.0.14393.8524 (Server 2016), 10.0.17763.7922 (Server 2019), 10.0.20348.4297 (Server 2022), 10.0.25398.1916 (Server 2022 23h2), or 10.0.26100.6905 (Server 2025); or if running Server 2012/R2 (all versions are affected)
  2. Verify WSUS is installed
    Check if the WSUS service exists by running 'Get-Service -Name WSUS' in PowerShell, or look for the WSUS virtual directories in IIS (typically under Default Web Site)
    Affected if WSUS service is present and installed on the system
  3. Confirm WSUS is running
    Run 'Get-Service -Name WSUS' or check Services.msc to see if the Windows Server Update Service is in a Running state
    Affected if The WSUS service is currently running
  4. Check WSUS configuration for network exposure
    Inspect IIS Manager (inetmgr) for WSUS virtual directories (ClientWebService, SimpleAuthWebService, DSSAuthWebService, ServerSyncWebService, and Inventory) and verify if they are bound to external IP addresses or allowing anonymous access
    Affected if WSUS virtual directories are accessible from network endpoints without restriction

The system is affected if it runs a vulnerable Windows Server version (2012/R2, 2016, 2019, 2022, 2022 23h2, or 2025 below the fixed builds) AND has WSUS installed and running with network-accessible endpoints.

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.14393.8524 / 10.0.17763.7922 / 10.0.20348.4297 or later
Fixed in 10.0.14393.852410.0.17763.792210.0.20348.4297
Interim mitigation

Apply Microsoft security patches for CVE-2025-59287 immediately; restrict network access to WSUS servers and ensure they are not directly exposed to the internet until patched.

Recommended fix High confidence

Apply Microsoft security updates to reach the minimum build number for your Windows Server version; Windows Server 2012 (all versions) is end-of-life and requires migration to a supported version

  1. Identify the current Windows Server version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows Server release (2012, 2016, 2019, 2022, 2022 23h2, or 2025) is running
  3. For Windows Server 2016: Apply updates until the build reaches 10.0.14393.8524 or higher
  4. For Windows Server 2019: Apply updates until the build reaches 10.0.17763.7922 or higher
  5. For Windows Server 2022: Apply updates until the build reaches 10.0.20348.4297 or higher
  6. For Windows Server 2022 23h2: Apply updates until the build reaches 10.0.25398.1916 or higher
  7. For Windows Server 2025: Apply updates until the build reaches 10.0.26100.6905 or higher
  8. Run Windows Update or check Microsoft Catalog for the latest cumulative update
Caveat Windows Server 2012 has reached end-of-life and cannot be patched; migration to a supported Windows Server version is required

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

Fix this in Windows Server 2012 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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