CVE-2026-83912 |
high
|
7.8 |
0.0032
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83918 |
high
|
7.8 |
0.0032
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83919 |
high
|
7.8 |
0.0031
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83920 |
high
|
7.8 |
0.0032
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85318 |
high
|
7.8 |
0.0031
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83691 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83704 |
high
|
7.8 |
0.0047
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83758 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83583 |
high
|
7.8 |
0.0034
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83587 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83641 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83709 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83726 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83727 |
high
|
7.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83732 |
high
|
7.8 |
0.0038
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85829 |
high
|
7.8 |
0.0031
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85832 |
high
|
7.8 |
0.0036
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85833 |
high
|
7.8 |
0.0031
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85843 |
high
|
7.8 |
0.0036
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85848 |
high
|
7.8 |
0.0036
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85849 |
high
|
7.8 |
0.0047
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85860 |
high
|
7.8 |
0.0024
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85861 |
high
|
7.8 |
0.0024
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85863 |
high
|
7.8 |
0.0024
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-85864 |
high
|
7.8 |
0.0030
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83513 |
high
|
7.8 |
0.0038
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83514 |
high
|
7.8 |
0.0038
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-69966 |
high
|
7.8 |
0.0034
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83698 |
high
|
7.8 |
0.0036
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83699 |
high
|
7.8 |
0.0042
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-42976 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-42976 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-54984 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
1 PoC
|
CVE-2026-54984 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
1 PoC
|
CVE-2026-61349 |
high
|
7.8 |
0.0026
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61349 |
high
|
7.8 |
0.0026
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61353 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61353 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61364 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61364 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61365 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61365 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61367 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61367 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61925 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61925 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61926 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61926 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61930 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61930 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|