CVE-2026-70158 |
high
|
8.8 |
0.0096
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-70158 |
high
|
8.8 |
0.0096
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-70158 |
high
|
8.8 |
0.0096
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-70297 |
high
|
8.8 |
0.0116
|
Microsoft |
Skype for Business Server 2019 CU8 |
2046.0
< 7.0.2046.583
|
|
CVE-2026-70297 |
high
|
8.8 |
0.0116
|
Microsoft |
Skype for Business Server Subscription Edition CU1 |
2046.0
< 7.0.2046.889
|
|
CVE-2026-77910 |
high
|
8.8 |
0.0087
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 14 |
15.02.0.0
< 15.02.1544.050
|
|
CVE-2026-77910 |
high
|
8.8 |
0.0087
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 15 |
15.02.0.0
< 15.02.1748.055
|
|
CVE-2026-77910 |
high
|
8.8 |
0.0087
|
Microsoft |
Microsoft Exchange Server Subscription Edition RTM |
15.02.0.0
< 15.02.2562.056
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|