CVE-2026-69952 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69952 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69953 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69953 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69957 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69957 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69959 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69959 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69963 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69963 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69966 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69966 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70010 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70010 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70015 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70015 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70048 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70048 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70059 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70059 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70060 |
high
|
7.8 |
0.0042
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70060 |
high
|
7.8 |
0.0042
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70064 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70064 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70092 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70092 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70093 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70093 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70103 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70103 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70106 |
high
|
7.8 |
0.0050
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70106 |
high
|
7.8 |
0.0050
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70108 |
high
|
7.8 |
0.0050
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70108 |
high
|
7.8 |
0.0050
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70109 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70109 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70110 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70110 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70113 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70113 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70117 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70117 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70123 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70123 |
high
|
7.8 |
0.0034
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70131 |
high
|
7.8 |
0.0049
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70131 |
high
|
7.8 |
0.0049
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70132 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70132 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70138 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70138 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|