CVE-2026-78444 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-78449 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-78449 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-78450 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-78450 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69325 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69325 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69524 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69524 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69782 |
high
|
8.1 |
0.0054
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69782 |
high
|
8.1 |
0.0054
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69827 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69827 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69989 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69989 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70342 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70342 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70563 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-70563 |
high
|
8.1 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83838 |
high
|
8.0 |
0.0055
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-88121 |
high
|
8.0 |
0.0116
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-27912 |
high
|
8.0 |
0.0041
|
microsoft |
windows_server_2019 |
< 10.0.17763.8644
|
|
CVE-2026-42975 |
high
|
8.0 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50365 |
high
|
8.0 |
0.0054
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50502 |
high
|
8.0 |
0.0065
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-50683 |
high
|
8.0 |
0.0058
|
microsoft |
windows_server_2019 |
< 10.0.17763.9020
|
|
CVE-2026-69363 |
high
|
8.0 |
0.0075
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96844 |
high
|
8.0 |
0.0053
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-96844 |
high
|
8.0 |
0.0053
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-96844 |
high
|
8.0 |
0.0053
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69363 |
high
|
8.0 |
0.0075
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69363 |
high
|
8.0 |
0.0075
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-83838 |
high
|
8.0 |
0.0055
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83838 |
high
|
8.0 |
0.0055
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88121 |
high
|
8.0 |
0.0116
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-88121 |
high
|
8.0 |
0.0116
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-69332 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69332 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69346 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69346 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69427 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69427 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69462 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69462 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69503 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69503 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69512 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69512 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69619 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69619 |
high
|
8.0 |
—
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|