CVE-2026-61932 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61932 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61937 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61937 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62692 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62692 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62696 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62696 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62698 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62698 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62700 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62700 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62701 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62701 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62707 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62707 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62710 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62710 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62711 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62711 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62712 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62712 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62717 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62717 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62719 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62719 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62721 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62721 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62732 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62732 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62733 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62733 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62735 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
2 PoC
|
CVE-2026-62735 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
2 PoC
|
CVE-2026-62741 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62741 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62747 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62747 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62754 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62754 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62755 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62755 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62758 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62758 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62768 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62768 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62770 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62770 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62776 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62776 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|