What it is
Deserialization of untrusted data in Windows Server Update Service allows an unauthorized attacker to execute code over a network.
Vulnerability report
Windows Server Update Service (WSUS) Remote Code Execution Vulnerability
Microsoft / Windows Server 2012 · affected before 6.2.9200.25728
Decision summary
Direct answers before the deeper technical record.
What it is
Deserialization of untrusted data in Windows Server Update Service allows an unauthorized attacker to execute code over a network.
Have exploitation attempts been observed?
Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Also reported by third-party sources. Confidence is confirmed.
Who is affected?
Affected products include Microsoft / Windows Server 2012 and 12 other products, including affected before 6.2.9200.25728, affected before 6.3.9600.22826, and affected before 10.0.14393.8524.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
Deserialization of untrusted data in Windows Server Update Service allows an unauthorized attacker to execute code over a network.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CVE
A trusted third party reported exploitation attempts.
Nuclei Templates
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CVE First | 2026-06-01 10:42 UTC |
| CISA | 2026-06-02 14:05 UTC |
| The Shadowserver | 2026-06-04 00:00 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Nuclei template detected 01 Jun 2026.
View Nuclei template (opens in new tab)No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Scanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-59287.yaml | 01 Jun 2026 |
| Metasploit | https://github.com/rapid7/metasploit-framework/blob/master/modules/exploits/windows/http/wsus_deserialization_rce.rb | 14 Oct 2025 |
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
100.0%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
Recent mention · Huntress Blog
SMB1001 gives small businesses a cybersecurity standard with a finish line. See how its five tiers work and where Huntress maps to each control.
Read full advisoryRecent mention · Huntress Blog
SMB1001: How Huntress Maps to Each TierHuntress Blog · 06 Oct 2026
SMB1001 gives small businesses a cybersecurity standard with a finish line. See how its five tiers work and where Huntress maps to each control.
These PoCs are unverified and could contain malware. Use at your own risk.
nuclei · Created Unknown
Timeline
14:21 UTC
Public proof-of-concept code published
00:00 UTC
Exploitation attempts reported by an external source
14:05 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
15:34 UTC
Scanner coverage available
10:42 UTC
High-confidence, third-party report of exploitation attempts
17:01 UTC
Vulnerability disclosed publicly
00:00 UTC
Exploit module available
19:36 UTC
Identifier reserved by the CNA
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2025-59287
Sample API response{
"cve_id": "CVE-2025-59287",
"confidence": "Confirmed",
"cvss_score": 9.8,
"cvss_estimated": false,
"epss_score": 0.9998,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}