CVE-2026-83759 |
high
|
8.8 |
0.0092
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83759 |
high
|
8.8 |
0.0092
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83759 |
high
|
8.8 |
0.0092
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83759 |
high
|
8.8 |
0.0092
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-83923 |
high
|
8.8 |
0.0102
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83923 |
high
|
8.8 |
0.0102
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83923 |
high
|
8.8 |
0.0102
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-83716 |
high
|
8.8 |
0.0035
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83716 |
high
|
8.8 |
0.0035
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83716 |
high
|
8.8 |
0.0035
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83716 |
high
|
8.8 |
0.0035
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83728 |
high
|
8.8 |
0.0030
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-116165 |
high
|
8.8 |
0.0032
|
parse-community |
parse-server |
9.0.0
< 9.10.4-alpha.4
|
|
CVE-2026-116165 |
high
|
8.8 |
0.0032
|
parse-community |
parse-server |
0
< 8.6.101
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83725 |
high
|
8.8 |
0.0077
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2012 |
-
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2012 |
r2
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2016 |
< 10.0.14393.9612
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2019 |
< 10.0.17763.9376
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2022 |
< 10.0.20348.5761
|
|
CVE-2026-83688 |
high
|
8.8 |
0.0093
|
microsoft |
windows_server_2025 |
< 10.0.26100.33650
|
|
CVE-2026-101781 |
high
|
8.8 |
0.0039
|
oracle |
mysql_server |
< 8.4.12
|
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9121
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5499
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33296
|
1 PoC
|
CVE-2026-49179 |
high
|
8.8 |
0.0086
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33296
|
1 PoC
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9418
|
|
CVE-2026-62784 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9121
|
|