CVE-2026-83867 |
high
|
7.8 |
0.0041
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83867 |
high
|
7.8 |
0.0041
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83872 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83872 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83873 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83873 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83876 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83876 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83877 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83877 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83881 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83881 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83882 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83882 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83883 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83883 |
high
|
7.8 |
0.0038
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83896 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83896 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83902 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83902 |
high
|
7.8 |
0.0040
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83912 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83912 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83918 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83918 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83919 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83919 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83920 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83920 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83932 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-83932 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-84013 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-84013 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-84016 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-84016 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85318 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85318 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85327 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85327 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85332 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85332 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85338 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85338 |
high
|
7.8 |
0.0032
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85341 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85341 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85343 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85343 |
high
|
7.8 |
0.0035
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85356 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85356 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85358 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9376
|
|
CVE-2026-85358 |
high
|
7.8 |
0.0031
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9376
|
|