CVE-2026-88165 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96913 |
high
|
8.8 |
0.0037
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96917 |
high
|
8.8 |
0.0036
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
KEV
|
CVE-2026-96952 |
high
|
8.8 |
0.0090
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83851 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83784 |
high
|
8.8 |
0.0108
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83643 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83759 |
high
|
8.8 |
0.0092
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83923 |
high
|
8.8 |
0.0102
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83716 |
high
|
8.8 |
0.0035
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
1 PoC
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62785 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62785 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62790 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62790 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62795 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62795 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62816 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62816 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62817 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-100220 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-100220 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102203 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102203 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102214 |
high
|
8.8 |
0.0038
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102214 |
high
|
8.8 |
0.0038
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102217 |
high
|
8.8 |
0.0126
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102217 |
high
|
8.8 |
0.0126
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102225 |
high
|
8.8 |
0.0089
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-102225 |
high
|
8.8 |
0.0089
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-103575 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-105007 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-105007 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-108471 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|