CVE-2026-50460 |
high
|
8.1 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50686 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-56186 |
high
|
8.1 |
0.0111
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-62778 |
high
|
8.1 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9121
|
|
CVE-2026-62781 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9115
|
|
CVE-2026-62792 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9115
|
|
CVE-2026-62819 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9115
|
|
CVE-2026-62820 |
high
|
8.1 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9121
|
|
CVE-2026-62889 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9115
|
|
CVE-2026-65679 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9115
|
|
CVE-2026-65789 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9121
|
|
CVE-2026-65796 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9115
|
|
CVE-2026-66802 |
high
|
8.1 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9121
|
|
CVE-2026-71331 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9121
|
|
CVE-2026-69782 |
high
|
8.1 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9245
|
|
CVE-2026-100218 |
high
|
8.1 |
0.0082
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-108460 |
high
|
8.1 |
0.0076
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-69830 |
high
|
8.1 |
0.0048
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-69913 |
high
|
8.1 |
0.0068
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-70013 |
high
|
8.1 |
0.0066
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-70038 |
high
|
8.1 |
0.0075
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-70111 |
high
|
8.1 |
0.0084
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-70127 |
high
|
8.1 |
0.0082
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-84012 |
high
|
8.1 |
0.0067
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-85371 |
high
|
8.1 |
0.0067
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-85799 |
high
|
8.1 |
0.0066
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-85926 |
high
|
8.1 |
0.0066
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88171 |
high
|
8.1 |
0.0069
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88173 |
high
|
8.1 |
0.0051
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88174 |
high
|
8.1 |
0.0042
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83522 |
high
|
8.1 |
0.0080
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83914 |
high
|
8.1 |
0.0080
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83674 |
high
|
8.1 |
0.0071
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-62778 |
high
|
8.1 |
0.0054
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62778 |
high
|
8.1 |
0.0054
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62781 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62781 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62792 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62792 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62819 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62819 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62820 |
high
|
8.1 |
0.0054
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62820 |
high
|
8.1 |
0.0054
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62889 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-62889 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-65679 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-65679 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-65789 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-65789 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
|
CVE-2026-65796 |
high
|
8.1 |
0.0071
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|