Windows Server 2016 vulnerabilities: known CVEs & security history
Microsoft · Operating System · 3226 tracked CVEs · 112 actively exploited · updated September 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Windows Server 2016 release lines — 3226 in total, with 112 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Windows Server 2016's current status and the safe version to run.
Known Windows Server 2016 CVEs
Actively-exploited and most-severe first. Showing the top 80 of 3226. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2020-1350⚡ exploited | critical | 10 | 92% | 2020 |
| CVE-2026-33824⚡ exploited | critical | 9.8 | 56% | 2026 |
| CVE-2020-0646⚡ exploited | critical | 9.8 | 99% | 2020 |
| CVE-2017-8543⚡ exploited | critical | 9.8 | 74% | 2017 |
| CVE-2020-1040⚡ exploited | critical | 9 | 7% | 2020 |
| CVE-2024-49039⚡ exploited | high | 8.8 | 14% | 2024 |
| CVE-2024-43461⚡ exploited | high | 8.8 | 52% | 2024 |
| CVE-2022-41128⚡ exploited | high | 8.8 | 25% | 2022 |
| CVE-2021-40444⚡ exploited | high | 8.8 | 97% | 2021 |
| CVE-2021-34527⚡ exploited | high | 8.8 | 100% | 2021 |
| CVE-2021-26411⚡ exploited | high | 8.8 | 81% | 2021 |
| CVE-2020-1020⚡ exploited | high | 8.8 | 65% | 2020 |
| CVE-2019-0903⚡ exploited | high | 8.8 | 22% | 2019 |
| CVE-2019-0541⚡ exploited | high | 8.8 | 53% | 2019 |
| CVE-2018-0824⚡ exploited | high | 8.8 | 73% | 2018 |
| CVE-2017-8464⚡ exploited | high | 8.8 | 90% | 2017 |
| CVE-2017-0222⚡ exploited | high | 8.8 | 30% | 2017 |
| CVE-2017-0210⚡ exploited | high | 8.8 | 20% | 2017 |
| CVE-2017-0149⚡ exploited | high | 8.8 | 29% | 2017 |
| CVE-2017-0146⚡ exploited | high | 8.8 | 90% | 2017 |
| CVE-2017-0145⚡ exploited | high | 8.8 | 90% | 2017 |
| CVE-2017-0144⚡ exploited | high | 8.8 | 99% | 2017 |
| CVE-2017-0143⚡ exploited | high | 8.8 | 93% | 2017 |
| CVE-2016-7256⚡ exploited | high | 8.8 | 65% | 2016 |
| CVE-2016-7201⚡ exploited | high | 8.8 | 80% | 2016 |
| CVE-2016-7200⚡ exploited | high | 8.8 | 82% | 2016 |
| CVE-2020-0601⚡ exploited | high | 8.1 | 89% | 2020 |
| CVE-2017-0148⚡ exploited | high | 8.1 | 99% | 2017 |
| CVE-2017-0037⚡ exploited | high | 8.1 | 80% | 2017 |
| CVE-2026-85880⚡ exploited | high | 7.8 | — | 2026 |
| CVE-2026-56155⚡ exploited | high | 7.8 | 0% | 2026 |
| CVE-2024-38014⚡ exploited | high | 7.8 | 6% | 2024 |
| CVE-2024-35250⚡ exploited | high | 7.8 | 25% | 2024 |
| CVE-2023-21823⚡ exploited | high | 7.8 | 6% | 2023 |
| CVE-2023-23376⚡ exploited | high | 7.8 | 11% | 2023 |
| CVE-2022-41125⚡ exploited | high | 7.8 | 3% | 2022 |
| CVE-2022-41073⚡ exploited | high | 7.8 | 2% | 2022 |
| CVE-2022-37969⚡ exploited | high | 7.8 | 28% | 2022 |
| CVE-2022-30190⚡ exploited | high | 7.8 | 99% | 2022 |
| CVE-2021-43226⚡ exploited | high | 7.8 | 3% | 2021 |
| CVE-2021-36955⚡ exploited | high | 7.8 | 3% | 2021 |
| CVE-2021-34484⚡ exploited | high | 7.8 | 16% | 2021 |
| CVE-2021-33771⚡ exploited | high | 7.8 | 6% | 2021 |
| CVE-2021-31979⚡ exploited | high | 7.8 | 3% | 2021 |
| CVE-2021-1675⚡ exploited | high | 7.8 | 85% | 2021 |
| CVE-2020-1147⚡ exploited | high | 7.8 | 96% | 2020 |
| CVE-2020-0986⚡ exploited | high | 7.8 | 16% | 2020 |
| CVE-2020-1027⚡ exploited | high | 7.8 | 4% | 2020 |
| CVE-2020-0938⚡ exploited | high | 7.8 | 69% | 2020 |
| CVE-2020-0787⚡ exploited | high | 7.8 | 43% | 2020 |
| CVE-2020-0683⚡ exploited | high | 7.8 | 8% | 2020 |
| CVE-2019-1458⚡ exploited | high | 7.8 | 74% | 2019 |
| CVE-2019-1405⚡ exploited | high | 7.8 | 30% | 2019 |
| CVE-2019-1388⚡ exploited | high | 7.8 | 9% | 2019 |
| CVE-2019-1385⚡ exploited | high | 7.8 | 4% | 2019 |
| CVE-2019-1315⚡ exploited | high | 7.8 | 3% | 2019 |
| CVE-2019-1215⚡ exploited | high | 7.8 | 19% | 2019 |
| CVE-2019-1214⚡ exploited | high | 7.8 | 1% | 2019 |
| CVE-2019-1130⚡ exploited | high | 7.8 | 2% | 2019 |
| CVE-2019-0880⚡ exploited | high | 7.8 | 2% | 2019 |
| CVE-2019-1069⚡ exploited | high | 7.8 | 6% | 2019 |
| CVE-2019-1064⚡ exploited | high | 7.8 | 7% | 2019 |
| CVE-2019-0863⚡ exploited | high | 7.8 | 5% | 2019 |
| CVE-2019-0859⚡ exploited | high | 7.8 | 4% | 2019 |
| CVE-2019-0841⚡ exploited | high | 7.8 | 42% | 2019 |
| CVE-2019-0803⚡ exploited | high | 7.8 | 45% | 2019 |
| CVE-2019-0797⚡ exploited | high | 7.8 | 2% | 2019 |
| CVE-2019-0543⚡ exploited | high | 7.8 | 5% | 2019 |
| CVE-2018-8639⚡ exploited | high | 7.8 | 22% | 2018 |
| CVE-2018-8611⚡ exploited | high | 7.8 | 4% | 2018 |
| CVE-2018-8453⚡ exploited | high | 7.8 | 70% | 2018 |
| CVE-2018-8440⚡ exploited | high | 7.8 | 19% | 2018 |
| CVE-2018-8406⚡ exploited | high | 7.8 | 3% | 2018 |
| CVE-2018-8405⚡ exploited | high | 7.8 | 3% | 2018 |
| CVE-2017-8759⚡ exploited | high | 7.8 | 89% | 2017 |
| CVE-2017-8540⚡ exploited | high | 7.8 | 72% | 2017 |
| CVE-2017-0263⚡ exploited | high | 7.8 | 10% | 2017 |
| CVE-2017-0005⚡ exploited | high | 7.8 | 11% | 2017 |
| CVE-2017-0001⚡ exploited | high | 7.8 | 3% | 2017 |
| CVE-2016-7255⚡ exploited | high | 7.8 | 81% | 2016 |
3146 older / lower-severity CVEs not shown — see Windows Server 2016's full record.
Is my Windows Server 2016 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 2016 version → · Monitor Windows Server 2016 for new CVEs →
Windows Server 2016 vulnerabilities — frequently asked
How many known vulnerabilities does Windows Server 2016 have?
IsItPatched tracks 3226 CVEs for Windows Server 2016, 112 of which are actively exploited (CISA KEV). 82 are critical-severity and 2198 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Windows Server 2016 have any actively-exploited vulnerabilities?
Yes — 112 Windows Server 2016 CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (47 linked to ransomware). Patch these as a priority.
What is the most severe Windows Server 2016 vulnerability?
Among tracked issues, CVE-2020-1350 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Improper input validation weakness.
Is Windows Server 2016 safe to use?
It depends on the version. The latest supported Windows Server 2016 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 2016 security status · Windows Server 2016 end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.