CVE-2026-56175 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56175 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56176 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56176 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56176 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56176 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56182 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56182 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56182 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56182 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56189 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56189 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56189 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56189 |
high
|
7.8 |
0.0039
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56650 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56650 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-56650 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-56650 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-57096 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-57096 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58532 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58532 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58532 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58532 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58540 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58540 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58540 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58540 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58609 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58609 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26226
|
|
CVE-2026-58609 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-58609 |
high
|
7.8 |
0.0047
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23291
|
|
CVE-2026-61353 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61353 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61353 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61353 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61367 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61367 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61367 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61367 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61925 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61925 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61925 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61925 |
high
|
7.8 |
0.0030
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61937 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61937 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-61937 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-61937 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23338
|
|
CVE-2026-62692 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26280
|
|
CVE-2026-62692 |
high
|
7.8 |
0.0033
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26280
|
|