CVE-2026-62817 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62817 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5499
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62818 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5499
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62822 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5499
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62823 |
high
|
8.8 |
0.0053
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
|
CVE-2026-62824 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62824 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62824 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62824 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62824 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62824 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62827 |
high
|
8.8 |
0.0094
|
Microsoft |
Microsoft SharePoint Server 2019 |
16.0.0
< 16.0.10417.20198
|
|
CVE-2026-62827 |
high
|
8.8 |
0.0094
|
Microsoft |
Microsoft SharePoint Server Subscription Edition |
16.0.0
< 16.0.19725.20522
|
|
CVE-2026-62913 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 14 |
15.02.0.0
< 15.02.1544.044
|
|
CVE-2026-62913 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 15 |
15.02.0.0
< 15.02.1748.049
|
|
CVE-2026-62913 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server Subscription Edition RTM |
15.02.0.0
< 15.02.2562.046
|
|
CVE-2026-63514 |
high
|
8.8 |
0.0204
|
Microsoft |
Microsoft SharePoint Server 2019 |
16.0.0
< 16.0.10417.20198
|
|
CVE-2026-63514 |
high
|
8.8 |
0.0204
|
Microsoft |
Microsoft SharePoint Server Subscription Edition |
16.0.0
< 16.0.19725.20522
|
|
CVE-2026-64901 |
high
|
8.8 |
0.0204
|
Microsoft |
Microsoft SharePoint Server 2019 |
16.0.0
< 16.0.10417.20198
|
|
CVE-2026-64901 |
high
|
8.8 |
0.0204
|
Microsoft |
Microsoft SharePoint Server Subscription Edition |
16.0.0
< 16.0.19725.20522
|
|
CVE-2026-64921 |
high
|
8.8 |
0.0094
|
Microsoft |
Microsoft SharePoint Server 2019 |
16.0.0
< 16.0.10417.20198
|
|