Patch tracker / KB5072014
KB5072014: Windows Server 2025 Security Update (December 2025)
KB5072014 is a High security update for Windows Server 2025, released 2025-12-09. It closes 33 CVEs with a maximum CVSS of 8.8. At least one of them is actively exploited (CISA KEV) and linked to ransomware, so it is urgent, and Microsoft lists 1 known issue: test it before broad deployment. It is the second largest of the 36 updates Microsoft shipped that month, by CVEs closed.
Before you deploy: Microsoft lists 1 known issue for this update.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Update summary
Fixes 33 CVEs. At least one is actively exploited (CISA KEV). Most severe CVSS 8.8 (High). EPSS exploit probability up to 4.6%. One is linked to ransomware. Among the top half of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Windows 11 Version 25H2 for ARM64-based Systems has shipped since this one: KB5127648 (2026-10-13). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 1 known issue with this update.
- Windows Server Update Services (WSUS) does not display error details
KB5072014 is a December 2025 rollup covering Windows 11 25H2 (ARM64 and x64) and Windows 10 1809, fixing 33 CVEs with a highest severity of High (CVSS 8.8). What stands out is that one of these CVEs is already listed in the CISA Known Exploited Vulnerabilities catalog, though none are tied to ransomware and peak EPSS remains low at 5%. The confirmed exploitation is what moves this from routine patching to a near-term priority.
Do this: Deploy KB5072014 to your 25H2 and 1809 fleet now, prioritizing internet-facing and privileged systems given the CISA KEV listing.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for KB5072014
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5072014
- Released
- 2025-12-09
- Last changed
- 2026-10-14
- Changes tracked
- 4
Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.
Check if KB5072014 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5072014 (checked 2026-10-15). Microsoft lists 1 known issue. Verify against the article before acting.
Windows Server Update Services (WSUS) does not display error details
After installing KB5070893 or later updates, Windows Server Update Services (WSUS) does not display synchronization error details within its error reporting. This functionality is temporarily removed to address the Remote Code Execution Vulnerability, CVE-2025-59287 .
Some Hotpatch-enabled machines might receive security updates that require a restart
Symptoms
The out-of-band update for Windows Server 2025 ( KB5070881 ) was briefly offered to all Windows Server 2025 machines, regardless of Hotpatch enrollment.
Machines that installed KB5070881 will temporarily stop receiving Hotpatch updates and will instead receive security updates that require a restart.
Workaround
This issue is addressed in KB5073379 .
CVEs fixed by this update
Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2025-60710 | High | 7.8 | 4.6% | KEV Ransomware |
| CVE-2025-62221 | High | 7.8 | 4.6% | KEV |
| CVE-2025-62456 | High | 8.8 | 4.6% | No |
| CVE-2025-62549 | High | 8.8 | 4.6% | No |
| CVE-2025-55233 | High | 7.8 | 4.6% | No |
| CVE-2025-59516 | High | 7.8 | 4.6% | No |
| CVE-2025-59517 | High | 7.8 | 4.6% | No |
| CVE-2025-62454 | High | 7.8 | 4.6% | No |
| CVE-2025-62457 | High | 7.8 | 4.6% | No |
| CVE-2025-62461 | High | 7.8 | 4.6% | No |
| CVE-2025-62462 | High | 7.8 | 4.6% | No |
| CVE-2025-62464 | High | 7.8 | 4.6% | No |
| CVE-2025-62466 | High | 7.8 | 4.6% | No |
| CVE-2025-62467 | High | 7.8 | 4.6% | No |
| CVE-2025-62470 | High | 7.8 | 4.6% | No |
| CVE-2025-62472 | High | 7.8 | 4.6% | No |
| CVE-2025-62474 | High | 7.8 | 4.6% | No |
| CVE-2025-62571 | High | 7.8 | 4.6% | No |
| CVE-2025-62572 | High | 7.8 | 4.6% | No |
| CVE-2025-64661 | High | 7.8 | 4.6% | No |
| CVE-2025-64673 | High | 7.8 | 4.6% | No |
| CVE-2025-64658 | High | 7.5 | 4.6% | No |
| CVE-2025-62565 | High | 7.3 | 4.6% | No |
| CVE-2025-62570 | High | 7.1 | 4.6% | No |
| CVE-2025-62469 | High | 7.0 | 4.6% | No |
| CVE-2025-62569 | High | 7.0 | 4.6% | No |
| CVE-2025-62573 | High | 7.0 | 4.6% | No |
| CVE-2025-62463 | Medium | 6.5 | 4.6% | No |
| CVE-2025-62465 | Medium | 6.5 | 4.6% | No |
| CVE-2025-62473 | Medium | 6.5 | 4.6% | No |
| CVE-2025-64670 | Medium | 6.5 | 4.6% | No |
| CVE-2025-62468 | Medium | 5.5 | 4.6% | No |
| CVE-2025-62567 | Medium | 5.3 | 4.6% | No |
Scope and sources
- Affected products
- Also released in December 2025
KB5071413
28 CVEs · High · exploitedKB5071417
30 CVEs · High · exploitedKB5071542
30 CVEs · High · exploitedKB5071544
26 CVEs · High · exploitedKB5071546
28 CVEs · High · exploitedKB5071547
29 CVEs · High · exploitedKB5072033
34 CVEs · High · exploitedKB5002815
1 CVE · HighThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.