CVE-2026-71352 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-71352 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-71352 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-71352 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72933 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72950 |
high
|
8.8 |
0.0092
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72959 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-72960 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-73006 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|