# CVE-2025-59287: Microsoft Windows Server Update Service (WSUS) Deserialization of Untrusted Data

> An unauthorized attacker can execute arbitrary code remotely via deserialization in Windows Server Update Service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 24 Oct 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-943j-4893-6rfq

## What is CVE-2025-59287?

CVE-2025-59287 is a critical unsafe deserialization vulnerability in Microsoft Windows Server 2012, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Deserialization of untrusted data in Windows Server Update Service allows an unauthorized attacker to execute code over a network.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-59287?

It affects 6 products.


Products: Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-59287?

No fix has been published for CVE-2025-59287 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Nov 2025.

## Is CVE-2025-59287 being exploited?

Yes. Attackers have exploited CVE-2025-59287 in the wild since at least 24 Oct 2025.

Public exploit code:

- WSUS Unauthenticated RCE (github_poc): https://github.com/jiansiting/CVE-2025-59287
- Helps defenders find their WSUS configurations in the wake of CVE-2025-59287 (github_poc): https://github.com/mubix/Find-WSUS
- Defensive PoC decoy for CVE-2025-59287 (WSUS) - emulates WSUS endpoints, captures request bodies and metadata, saves evidence for forensic analysis, and provides validation harness and detection rules. (github_poc): https://github.com/Lupovis/Honeypot-for-CVE-2025-59287-WSUS
- powershell version of hawktrace POC exploit (github_poc): https://github.com/tecxx/CVE-2025-59287-WSUS
- Working exploit (PoC) for CVE-2025-59287 — WSUS vulnerability. Featured on Vulners and DeepWiki. (github_poc): https://github.com/garvitv14/CVE-2025-59287
- Unauthenticated RCE PoC in Microsoft Windows Server Update Service (WSUS) - CVE-2025-59287 & CVE-2023-35317 (github_poc): https://github.com/M507/CVE-2025-59287-PoC

## Other vulnerabilities in Microsoft Windows Server 2012

- [CVE-2026-69595](https://insights.sbomify.com/CVE-2026-69595/): Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-78445](https://insights.sbomify.com/CVE-2026-78445/): Windows Services for NFS ONCRPC XDR Driver Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-41089](https://insights.sbomify.com/CVE-2026-41089/): Windows Netlogon Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2024-43639](https://insights.sbomify.com/CVE-2024-43639/): Windows KDC Proxy Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2023-24941](https://insights.sbomify.com/CVE-2023-24941/): Windows Network File System Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59287 and fix it if it is affected.

What it is: CVE-2025-59287 is a critical unsafe deserialization vulnerability in Microsoft Windows Server 2012, published on 14 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-59287 in the wild since at least 24 Oct 2025.

Affected product: Microsoft Windows Server 2012. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59287/ (Markdown: https://insights.sbomify.com/CVE-2025-59287/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59287
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59287
- OSV: https://osv.dev/vulnerability/CVE-2025-59287

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59287/
Summaries are generated and may contain mistakes; the official description above is the record.