CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 11 version 26H1 |
10.0.28000.0
< 10.0.28000.2525
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5386
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33158
|
|
CVE-2026-57094 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33158
|
|
CVE-2026-57102 |
high
|
8.8 |
0.0082
|
Microsoft |
Visual Studio Code |
1.0.0
< 1.128.1
|
|
CVE-2026-57104 |
high
|
8.8 |
0.0086
|
Microsoft |
Azure Storage Explorer |
0
< 1.45.0
|
|
CVE-2026-57969 |
high
|
8.8 |
0.0078
|
Microsoft |
Azure CycleCloud 8.9.1 |
1.0.0
< 8.9.1
|
|
CVE-2026-57974 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57981 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58277 |
high
|
8.8 |
0.0094
|
Microsoft |
Microsoft SharePoint Enterprise Server 2016 |
16.0.0
< 16.0.5561.1001
|
|
CVE-2026-58277 |
high
|
8.8 |
0.0094
|
Microsoft |
Microsoft SharePoint Server 2019 |
16.0.0
< 16.0.10417.20175
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 10 Version 1607 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 10 Version 1809 |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 10 Version 21H2 |
10.0.19044.0
< 10.0.19044.7548
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 10 Version 22H2 |
10.0.19045.0
< 10.0.19045.7548
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 11 Version 24H2 |
10.0.26100.0
< 10.0.26100.8875
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 11 Version 25H2 |
10.0.26200.0
< 10.0.26200.8875
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows 11 version 26H1 |
10.0.28000.0
< 10.0.28000.2525
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5386
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33158
|
|
CVE-2026-58534 |
high
|
8.8 |
0.0033
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33158
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 10 Version 1607 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 10 Version 1809 |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 10 Version 21H2 |
10.0.19044.0
< 10.0.19044.7548
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 10 Version 22H2 |
10.0.19045.0
< 10.0.19045.7548
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 11 Version 24H2 |
10.0.26100.0
< 10.0.26100.8875
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 11 Version 25H2 |
10.0.26200.0
< 10.0.26200.8875
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows 11 version 26H1 |
10.0.28000.0
< 10.0.28000.2525
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5386
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33158
|
|
CVE-2026-58594 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33158
|
|
CVE-2026-58608 |
high
|
8.8 |
0.0057
|
Microsoft |
Windows 10 Version 1607 |
10.0.14393.0
< 10.0.14393.9339
|
|
CVE-2026-58608 |
high
|
8.8 |
0.0057
|
Microsoft |
Windows 10 Version 1809 |
10.0.17763.0
< 10.0.17763.9020
|
|
CVE-2026-58608 |
high
|
8.8 |
0.0057
|
Microsoft |
Windows 10 Version 21H2 |
10.0.19044.0
< 10.0.19044.7548
|
|