Windows Server vulnerabilitiesAnd the versions its exploited flaws hit.
Windows Server is made by Microsoft. We track 305 published vulnerabilities listed under that exact name, across 10 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 6 October 2025. Microsoft lists newer releases under their own names, such as Windows Server 2016, so check those pages too.
The most recent Windows Server flaw added to the known-exploited list is CVE-2021-43226, on 6 October 2025. We keep watching the known-exploited list.
Is Windows Server listed under other names? Yes.
Microsoft also lists Windows Server under more specific names, such as Windows Server 2016 and Windows Server 2019. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
- Windows Server 20164,711 published vulnerabilities
- Windows Server 20194,111 published vulnerabilities
- Windows Server 20083,906 published vulnerabilities
- Windows Server 20123,842 published vulnerabilities
- Windows Server 20222,137 published vulnerabilities
- Windows Server 2022 23H21,060 published vulnerabilities
- Windows Server 2003653 published vulnerabilities
- Windows Server 2025549 published vulnerabilities
- Windows Server 20H252 published vulnerabilities
- Windows Server 180334 published vulnerabilities
- Windows Server 200426 published vulnerabilities
- Windows Server 190325 published vulnerabilities
Which versions of Windows Server do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2021-43226Exploited list, 6 Oct 2025
Microsoft Windows Privilege Escalation Vulnerability
20h22022 - CVE-2012-4969Exploited list, 8 Jun 2022
Microsoft Internet Explorer Use-After-Free Vulnerability
2003-sp22008-sp2
Which Windows Server vulnerabilities are being exploited?
2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 7.8Microsoft Windows Privilege Escalation Vulnerability
Microsoft Windows Common Log File System Driver contains a privilege escalation vulnerability that could allow a local, privileged attacker to bypass certain security mechanisms.
- 8.1Microsoft Internet Explorer Use-After-Free Vulnerability
Microsoft Internet Explorer contains a use-after-free vulnerability that allows remote attackers to execute code via a crafted web site.
Which Windows Server flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 93%CVE-2022-21907Critical
HTTP Protocol Stack Remote Code Execution Vulnerability
- 80%
Use-after-free vulnerability in the CMshtmlEd::Exec function in mshtml.dll in Microsoft Internet Explorer 6 through 9 allows remote attackers to execute arbitrary code via a crafted web site, as exploited in the wild...
- 79%CVE-2022-21972High
Windows Point-to-Point Tunneling Protocol Remote Code Execution Vulnerability
- 76%CVE-2022-26937Critical
Windows Network File System Remote Code Execution Vulnerability
- 70%CVE-2022-23270High
Windows Point-to-Point Tunneling Protocol Remote Code Execution Vulnerability
- 70%CVE-2017-11873High
ChakraCore and Microsoft Edge in Windows 10 1511, 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709 allows an attacker to gain the same user rights as the current user, due to how the scripting...
- 64%CVE-2017-11861High
Microsoft Edge in Windows 10 1607, 1703, 1709, Windows Server 2016 and Windows Server, version 1709 allows an attacker to gain the same user rights as the current user, due to how the scripting engine handles objects...
- 60%CVE-2017-11870High
ChakraCore and Microsoft Edge in Windows 10 1703, 1709, and Windows Server, version 1709 allows an attacker to gain the same user rights as the current user, due to how the scripting engine handles objects in memory,...
- 56%CVE-2022-23253Medium
Windows Point-to-Point Tunneling Protocol Denial of Service Vulnerability
- 50%CVE-2021-26414Medium
Windows DCOM Server Security Feature Bypass
Running Windows Server? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
Microsoft Windows Common Log File System Driver contains a privilege escalation vulnerability that could allow a local, privileged attacker to bypass certain security mechanisms.
- Matched to
- Windows Server on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 305 published vulnerabilities listed under the name Windows Server, across 10 versions. The most recent Windows Server flaw added to the known-exploited list is CVE-2021-43226, on 6 October 2025.
2 are on the list of flaws known to be exploited. The most recently added are CVE-2021-43226 and CVE-2012-4969.
Microsoft also lists Windows Server under more specific names, such as Windows Server 2016 and Windows Server 2019. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Each flaw names its own versions, usually as ranges. The newest, CVE-2021-43226, affects 20h2, 2022. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Windows Server. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.