CVE-2026-87712 |
high
|
7.8 |
0.0024
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-87712 |
high
|
7.8 |
0.0024
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88070 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88070 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88080 |
high
|
7.8 |
0.0024
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88080 |
high
|
7.8 |
0.0024
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88091 |
high
|
7.8 |
0.0293
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88091 |
high
|
7.8 |
0.0293
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88101 |
high
|
7.8 |
0.0021
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88101 |
high
|
7.8 |
0.0021
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88118 |
high
|
7.8 |
0.0041
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88118 |
high
|
7.8 |
0.0041
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88126 |
high
|
7.8 |
0.0036
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88126 |
high
|
7.8 |
0.0036
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88134 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88134 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88135 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88135 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88147 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88147 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88152 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88152 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96217 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96217 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96244 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96244 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96306 |
high
|
7.8 |
0.0024
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96306 |
high
|
7.8 |
0.0024
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96308 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96308 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96312 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96312 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96318 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96318 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96856 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96856 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96862 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96862 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96867 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96867 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96920 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96920 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96928 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96928 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69290 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69290 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69298 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69298 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69312 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69312 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|