Windows Server 2016 vulnerabilities: known CVEs & security history
Microsoft · Operating System · 2000 tracked CVEs · 73 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Windows Server 2016 release lines — 2000 in total, with 73 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 2000. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2020-1350⚡ exploited | critical | 10 | 92% | 2020 |
| 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-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-2020-1147⚡ exploited | high | 7.8 | 96% | 2020 |
| CVE-2020-0986⚡ exploited | high | 7.8 | 16% | 2020 |
| CVE-2020-1054⚡ exploited | high | 7.8 | 53% | 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 | 3% | 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 | 73% | 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 |
| CVE-2020-0968⚡ exploited | high | 7.5 | 30% | 2020 |
| CVE-2020-0674⚡ exploited | high | 7.5 | 87% | 2020 |
| CVE-2019-1429⚡ exploited | high | 7.5 | 73% | 2019 |
| CVE-2019-1367⚡ exploited | high | 7.5 | 53% | 2019 |
| CVE-2019-0752⚡ exploited | high | 7.5 | 82% | 2019 |
| CVE-2018-8653⚡ exploited | high | 7.5 | 29% | 2018 |
| CVE-2018-8373⚡ exploited | high | 7.5 | 62% | 2018 |
| CVE-2018-8174⚡ exploited | high | 7.5 | 88% | 2018 |
| CVE-2017-0147⚡ exploited | high | 7.5 | 100% | 2017 |
| CVE-2017-0213⚡ exploited | high | 7.3 | 84% | 2017 |
| CVE-2019-0703⚡ exploited | medium | 6.5 | 10% | 2019 |
| CVE-2019-0676⚡ exploited | medium | 6.5 | 8% | 2019 |
| CVE-2017-0022⚡ exploited | medium | 6.5 | 18% | 2017 |
| CVE-2013-3900⚡ exploited | medium | 5.5 | 45% | 2013 |
| CVE-2017-0059⚡ exploited | medium | 4.3 | 62% | 2017 |
| CVE-2019-14678 | critical | 10 | 3% | 2019 |
| CVE-2020-1112 | critical | 9.9 | 4% | 2020 |
| CVE-2019-1384 | critical | 9.9 | 6% | 2019 |
| CVE-2019-1365 | critical | 9.9 | 4% | 2019 |
| CVE-2020-0690 | critical | 9.8 | 7% | 2020 |
| CVE-2020-0610 | critical | 9.8 | 65% | 2020 |
| CVE-2020-0609 | critical | 9.8 | 75% | 2020 |
1920 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 2000 CVEs for Windows Server 2016, 73 of which are actively exploited (CISA KEV). 41 are critical-severity and 1335 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 — 73 Windows Server 2016 CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (27 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.