CVE-2026-83770 |
critical
|
9.8 |
0.0110
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-83770 |
critical
|
9.8 |
0.0110
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-83770 |
critical
|
9.8 |
0.0110
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83770 |
critical
|
9.8 |
0.0110
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83770 |
critical
|
9.8 |
0.0110
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83770 |
critical
|
9.8 |
0.0110
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-69705 |
critical
|
9.8 |
0.0095
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-69705 |
critical
|
9.8 |
0.0095
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-69705 |
critical
|
9.8 |
0.0095
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-69705 |
critical
|
9.8 |
0.0095
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-69705 |
critical
|
9.8 |
0.0095
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-69705 |
critical
|
9.8 |
0.0095
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-4052 |
critical
|
9.8 |
0.0036
|
WSO2 |
WSO2 Identity Server Key Manager Connector (apim-km-wso2is) |
0
< 1.8.8
|
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.3406
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.3406
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.1006
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.5356
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.5356
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2008 Service Pack 2 |
6.0.6003.0
< 6.0.6003.21666
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2008 Service Pack 2 (Server Core installation) |
6.0.6003.0
< 6.0.6003.21666
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2008 Service Pack 2 |
6.0.6003.0
< 6.0.6003.21666
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2008 R2 Service Pack 1 |
6.1.7601.0
< 6.1.7601.26115
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2008 R2 Service Pack 1 (Server Core installation) |
6.1.7601.0
< 6.1.7601.26115
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.23865
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.23865
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.20571
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.20571
|
1 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2008 Service Pack 2 |
6.0.6003.0
< 6.0.6003.23016
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2008 R2 Service Pack 1 |
6.1.7601.0
< 6.1.7601.27467
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2008 R2 Service Pack 1 (Server Core installation) |
6.1.7601.0
< 6.1.7601.27467
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2008 Service Pack 2 |
6.0.6003.0
< 6.0.6003.23016
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2008 Service Pack 2 (Server Core installation) |
6.0.6003.0
< 6.0.6003.23016
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.25222
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.25222
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.22318
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.22318
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.7606
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.7606
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.6659
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.6659
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.2966
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2022, 23H2 Edition (Server Core installation) |
10.0.25398.0
< 10.0.25398.1308
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.2605
|
3 PoC
|
CVE-2024-49112 |
critical
|
9.8 |
0.7217
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.2605
|
3 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
microsoft |
windows_server_2008 |
-
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
microsoft |
windows_server_2008 |
r2
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
microsoft |
windows_server_2012 |
-
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
microsoft |
windows_server_2012 |
r2
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
microsoft |
windows_server_2016 |
-
|
1 PoC
|
CVE-2022-34718 |
critical
|
9.8 |
0.5470
|
microsoft |
windows_server_2019 |
-
|
1 PoC
|