Windows Server 2025 vulnerabilities: known CVEs & security history
Microsoft · Operating System · 2208 tracked CVEs · 15 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Windows Server 2025 release lines — 2208 in total, with 15 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Windows Server 2025's current status and the safe version to run.
Known Windows Server 2025 CVEs
Actively-exploited and most-severe first. Showing the top 80 of 2208. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2026-33824⚡ exploited | critical | 9.8 | 2% | 2026 |
| CVE-2026-96951⚡ exploited | high | 8.8 | 2% | 2026 |
| CVE-2024-49039⚡ exploited | high | 8.8 | 14% | 2024 |
| CVE-2026-81963⚡ exploited | high | 7.8 | — | 2026 |
| CVE-2026-56155⚡ exploited | high | 7.8 | 0% | 2026 |
| CVE-2025-62221⚡ exploited | high | 7.8 | 3% | 2025 |
| CVE-2025-60710⚡ exploited | high | 7.8 | 5% | 2025 |
| CVE-2025-24993⚡ exploited | high | 7.8 | 2% | 2025 |
| CVE-2025-21335⚡ exploited | high | 7.8 | 1% | 2025 |
| CVE-2025-21391⚡ exploited | high | 7.1 | 2% | 2025 |
| CVE-2026-68820⚡ exploited | high | 7 | 0% | 2026 |
| CVE-2025-26633⚡ exploited | high | 7 | 30% | 2025 |
| CVE-2026-20805⚡ exploited | medium | 5.5 | 5% | 2026 |
| CVE-2013-3900⚡ exploited | medium | 5.5 | 45% | 2013 |
| CVE-2026-32202⚡ exploited | medium | 4.3 | 71% | 2026 |
| CVE-2026-57092 | critical | 9.9 | 1% | 2026 |
| CVE-2026-97816 | critical | 9.8 | 1% | 2026 |
| CVE-2026-97815 | critical | 9.8 | 1% | 2026 |
| CVE-2026-97814 | critical | 9.8 | 1% | 2026 |
| CVE-2026-97805 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96934 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96924 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96909 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96320 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96219 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96113 | critical | 9.8 | 1% | 2026 |
| CVE-2026-96096 | critical | 9.8 | 1% | 2026 |
| CVE-2026-88102 | critical | 9.8 | 1% | 2026 |
| CVE-2026-85814 | critical | 9.8 | 1% | 2026 |
| CVE-2026-85809 | critical | 9.8 | 1% | 2026 |
| CVE-2026-85806 | critical | 9.8 | 1% | 2026 |
| CVE-2026-85792 | critical | 9.8 | 1% | 2026 |
| CVE-2026-84015 | critical | 9.8 | 1% | 2026 |
| CVE-2026-83935 | critical | 9.8 | 1% | 2026 |
| CVE-2026-83869 | critical | 9.8 | 1% | 2026 |
| CVE-2026-70024 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69886 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69883 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69639 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69634 | critical | 9.8 | 1% | 2026 |
| CVE-2026-105010 | critical | 9.8 | 1% | 2026 |
| CVE-2026-102210 | critical | 9.8 | 1% | 2026 |
| CVE-2026-100222 | critical | 9.8 | 1% | 2026 |
| CVE-2026-100219 | critical | 9.8 | 1% | 2026 |
| CVE-2026-100202 | critical | 9.8 | 1% | 2026 |
| CVE-2026-78445 | critical | 9.8 | 1% | 2026 |
| CVE-2026-77493 | critical | 9.8 | 1% | 2026 |
| CVE-2026-73025 | critical | 9.8 | 1% | 2026 |
| CVE-2026-73010 | critical | 9.8 | 1% | 2026 |
| CVE-2026-73009 | critical | 9.8 | 1% | 2026 |
| CVE-2026-72983 | critical | 9.8 | 1% | 2026 |
| CVE-2026-72982 | critical | 9.8 | 1% | 2026 |
| CVE-2026-72979 | critical | 9.8 | 1% | 2026 |
| CVE-2026-70296 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69910 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69845 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69829 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69824 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69819 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69769 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69768 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69730 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69715 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69595 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69590 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69586 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69579 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69525 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69496 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69493 | critical | 9.8 | — | 2026 |
| CVE-2026-69491 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69463 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69431 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69408 | critical | 9.8 | 1% | 2026 |
| CVE-2026-69276 | critical | 9.8 | 1% | 2026 |
| CVE-2026-68839 | critical | 9.8 | 1% | 2026 |
| CVE-2026-65791 | critical | 9.8 | 1% | 2026 |
| CVE-2026-62893 | critical | 9.8 | 3% | 2026 |
| CVE-2026-62878 | critical | 9.8 | 1% | 2026 |
| CVE-2026-62815 | critical | 9.8 | 1% | 2026 |
2128 older / lower-severity CVEs not shown — see Windows Server 2025's full record.
Is my Windows Server 2025 version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Windows Server 2025 version → · Monitor Windows Server 2025 for new CVEs →
Windows Server 2025 vulnerabilities — frequently asked
How many known vulnerabilities does Windows Server 2025 have?
IsItPatched tracks 2208 CVEs for Windows Server 2025, 15 of which are actively exploited (CISA KEV). 84 are critical-severity and 1582 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Windows Server 2025 have any actively-exploited vulnerabilities?
Yes — 15 Windows Server 2025 CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (3 linked to ransomware). Patch these as a priority.
What is the most severe Windows Server 2025 vulnerability?
Among tracked issues, CVE-2026-33824 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Double free weakness.
Is Windows Server 2025 safe to use?
It depends on the version. The latest supported Windows Server 2025 release (10.0.26100) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Windows Server 2025 security status · Windows Server 2025 end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.