CVE-2026-96915 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96915 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96916 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96916 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96918 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96918 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96929 |
high
|
7.8 |
0.0048
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96929 |
high
|
7.8 |
0.0048
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96931 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96931 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96933 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96933 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96946 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96946 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96947 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96947 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96950 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96950 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96953 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96953 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-97804 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-97804 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-102227 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-102227 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-49785 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-49785 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-68836 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-68836 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69354 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69354 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69471 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69471 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69633 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69633 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69650 |
high
|
7.8 |
0.0025
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69650 |
high
|
7.8 |
0.0025
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69798 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69798 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69850 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69850 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69867 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69867 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69909 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69909 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69916 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69916 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69949 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69949 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69950 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69950 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|