CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (CU9) |
17.0.4006.2
< 17.0.5015.4
|
|
CVE-2026-65674 |
high
|
8.8 |
0.0162
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1145.4
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69326 |
high
|
8.8 |
0.0077
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69521 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69765 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69918 |
high
|
8.8 |
0.0041
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69945 |
high
|
8.8 |
0.0032
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-69945 |
high
|
8.8 |
0.0032
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69945 |
high
|
8.8 |
0.0032
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69985 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69985 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69985 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-69985 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-69985 |
high
|
8.8 |
0.0080
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33650
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26434
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23470
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9612
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5761
|
|
CVE-2026-70068 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33650
|
|