CVE-2026-108471 |
high
|
8.8 |
0.0037
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70158 |
high
|
8.8 |
0.0096
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70158 |
high
|
8.8 |
0.0096
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70250 |
high
|
8.8 |
0.0047
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88112 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88114 |
high
|
8.8 |
0.0070
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88116 |
high
|
8.8 |
0.0072
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88142 |
high
|
8.8 |
0.0085
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88142 |
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 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-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-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-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-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-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-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-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-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-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-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-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-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-70069 |
high
|
8.8 |
0.0103
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70069 |
high
|
8.8 |
0.0103
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70089 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70089 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70149 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70149 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70185 |
high
|
8.8 |
0.0030
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70185 |
high
|
8.8 |
0.0030
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70210 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70210 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-70258 |
high
|
8.8 |
0.0093
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|