CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-88219 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2017 for x64-based Systems (CU31) |
14.0.3006.16
< 14.0.3560.2
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2200.2
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2019 for x64-based Systems (CU32) |
15.0.4003.23
< 15.0.4500.2
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1210.3
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2022 for x64-based Systems (CU27) |
16.0.4003.1
< 16.0.4305.5
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-94512 |
high
|
8.8 |
0.0065
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-96230 |
high
|
8.8 |
0.0095
|
Microsoft |
Microsoft.AspNetCore.Components.WebAssembly.Server |
10.0.0
< 10.0.13
|
1 PoC
|
CVE-2026-96913 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96913 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96913 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-96913 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96913 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96914 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96917 |
high
|
8.8 |
0.0036
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96917 |
high
|
8.8 |
0.0036
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96917 |
high
|
8.8 |
0.0036
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-96917 |
high
|
8.8 |
0.0036
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96917 |
high
|
8.8 |
0.0036
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
KEV
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
KEV
|
CVE-2026-96952 |
high
|
8.8 |
0.0090
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96952 |
high
|
8.8 |
0.0090
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96952 |
high
|
8.8 |
0.0090
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|