CVE-2026-69323 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69323 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69324 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69324 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69328 |
high
|
7.8 |
0.0046
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69328 |
high
|
7.8 |
0.0046
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69352 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69352 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69407 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69407 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69421 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69421 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69424 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69424 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69426 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69426 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69433 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69433 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69444 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69444 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69445 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69445 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69456 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69456 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69475 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69475 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69489 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69489 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69509 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69509 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69538 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69538 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69561 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69561 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69571 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69571 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69584 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69584 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69592 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69592 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69593 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69593 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69612 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69612 |
high
|
7.8 |
0.0037
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69685 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69685 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69687 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69687 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69707 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69707 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|