CVE-2026-50695 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-50695 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-54113 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-54113 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-54119 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-54119 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-54983 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-54983 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-56648 |
high
|
7.5 |
0.0051
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-56648 |
high
|
7.5 |
0.0051
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58531 |
high
|
7.5 |
0.0051
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58531 |
high
|
7.5 |
0.0051
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58627 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58627 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-59132 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-59132 |
high
|
7.5 |
0.0117
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-59134 |
high
|
7.5 |
0.0068
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-59134 |
high
|
7.5 |
0.0068
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61352 |
high
|
7.5 |
0.0047
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-61352 |
high
|
7.5 |
0.0047
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62787 |
high
|
7.5 |
0.0066
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62787 |
high
|
7.5 |
0.0066
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-103558 |
high
|
7.5 |
0.0098
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-103558 |
high
|
7.5 |
0.0098
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-103569 |
high
|
7.5 |
0.0111
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-103569 |
high
|
7.5 |
0.0111
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-105009 |
high
|
7.5 |
0.0032
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-105009 |
high
|
7.5 |
0.0032
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-108131 |
high
|
7.5 |
0.0086
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-108131 |
high
|
7.5 |
0.0086
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96071 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96071 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96325 |
high
|
7.5 |
0.0105
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96325 |
high
|
7.5 |
0.0105
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-97788 |
high
|
7.5 |
0.0088
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-97788 |
high
|
7.5 |
0.0088
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-105723 |
high
|
7.5 |
0.0132
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-105723 |
high
|
7.5 |
0.0132
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69789 |
high
|
7.5 |
0.0046
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69789 |
high
|
7.5 |
0.0046
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69976 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69976 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69984 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69984 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69986 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69986 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69987 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69987 |
high
|
7.5 |
0.0063
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69988 |
high
|
7.5 |
0.0065
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69988 |
high
|
7.5 |
0.0065
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|