CVE-2026-96952 |
high
|
8.8 |
0.0090
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96952 |
high
|
8.8 |
0.0090
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-97004 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97007 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97008 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97010 |
high
|
8.8 |
0.0084
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97738 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97742 |
high
|
8.8 |
0.0093
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97746 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97748 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97756 |
high
|
8.8 |
0.0091
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97757 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97762 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97763 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97768 |
high
|
8.8 |
0.0086
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97769 |
high
|
8.8 |
0.0090
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97772 |
high
|
8.8 |
0.0084
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97773 |
high
|
8.8 |
0.0084
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97775 |
high
|
8.8 |
0.0084
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-97777 |
high
|
8.8 |
0.0084
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-105718 |
high
|
8.8 |
0.0095
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-105733 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-105733 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-105733 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-108446 |
high
|
8.8 |
0.0062
|
Microsoft |
Office Online Server |
16.0.0.0
< 16.0.10417.20228
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-108458 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-108467 |
high
|
8.8 |
0.0100
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1210.3
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|