CVE-2026-80096 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-80096 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-80096 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-80096 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9504
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9504
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-81955 |
high
|
8.8 |
0.0084
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-83992 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-62706 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-62744 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-62744 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-62895 |
high
|
8.8 |
0.0080
|
Microsoft |
Azure Arc SQL Server Extension |
1.0.0.0
< 1.1.3518.465
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2019 (CU 32) |
15.0.0.0
< 15.0.4490.9
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2019 (GDR) |
15.0.0
< 15.0.2190.7
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2022 (CU 26) |
16.0.0.0
< 16.0.4275.2
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2022 (GDR) |
16.0.0
< 16.0.1200.5
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2025 (CU8) |
17.0.0.0
< 17.0.4085.5
|
|
CVE-2026-66814 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2025 for x64-based Systems (GDR) |
17.0.1050.2
< 17.0.1135.8
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2017 (CU 31) |
14.0.0
< 14.0.3550.4
|
|
CVE-2026-66818 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SQL Server 2017 (GDR) |
14.0.0
< 14.0.2130.4
|
|