CVE-2026-62876 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62876 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62880 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62880 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62885 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62885 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62890 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62890 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62894 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62894 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65671 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65671 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65774 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65774 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65786 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65786 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65787 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65787 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65790 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65790 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65814 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-65814 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-66799 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-66799 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-70345 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-70345 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-70346 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-70346 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-70347 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-70347 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-27913 |
high
|
7.7 |
0.0030
|
microsoft |
windows_server_2016 |
< 10.0.14393.9060
|
|
CVE-2026-69789 |
high
|
7.5 |
0.0046
|
microsoft |
windows_server_2016 |
< 10.0.14393.9512
|
|
CVE-2026-69986 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-69987 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-69988 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-70006 |
high
|
7.5 |
0.0063
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-70058 |
high
|
7.5 |
0.0133
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-70133 |
high
|
7.5 |
0.0127
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-70207 |
high
|
7.5 |
0.0075
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83795 |
high
|
7.5 |
0.0127
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83843 |
high
|
7.5 |
0.0127
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85353 |
high
|
7.5 |
0.0098
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-96861 |
high
|
7.5 |
0.0112
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-96866 |
high
|
7.5 |
0.0112
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-26154 |
high
|
7.5 |
0.0106
|
microsoft |
windows_server_2016 |
< 10.0.14393.9060
|
|
CVE-2026-32071 |
high
|
7.5 |
0.0106
|
microsoft |
windows_server_2016 |
< 10.0.14393.9060
|
|
CVE-2026-40378 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|
CVE-2026-49171 |
high
|
7.5 |
0.0030
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|
CVE-2026-49181 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|
CVE-2026-49787 |
high
|
7.5 |
0.0117
|
microsoft |
windows_server_2016 |
< 10.0.14393.9339
|
|