CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-68828 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69266 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69268 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SharePoint Server Subscription Edition |
16.0.0
< 16.0.20326.20090
|
|
CVE-2026-69273 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SharePoint Server Subscription Edition |
16.0.0
< 16.0.20326.20082
|
|
CVE-2026-69282 |
high
|
8.8 |
0.0078
|
Microsoft |
Microsoft SharePoint Server Subscription Edition |
16.0.0
< 16.0.20326.20090
|
|
CVE-2026-69355 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server 2016 Cumulative Update 23 |
15.01.0.0
< 15.01.2507.073
|
|
CVE-2026-69355 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 14 |
15.02.0.0
< 15.02.1544.046
|
|
CVE-2026-69355 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server 2019 Cumulative Update 15 |
15.02.0.0
< 15.02.1748.051
|
|
CVE-2026-69355 |
high
|
8.8 |
0.0091
|
Microsoft |
Microsoft Exchange Server Subscription Edition RTM |
15.02.0.0
< 15.02.2562.049
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 (Server Core installation) |
6.3.9600.0
< 6.3.9600.23398
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69461 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2016 (Server Core installation) |
10.0.14393.0
< 10.0.14393.9512
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2019 (Server Core installation) |
10.0.17763.0
< 10.0.17763.9245
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2022 |
10.0.20348.0
< 10.0.20348.5622
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69485 |
high
|
8.8 |
0.0091
|
Microsoft |
Windows Server 2025 (Server Core installation) |
10.0.26100.0
< 10.0.26100.33438
|
|
CVE-2026-69494 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69494 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 (Server Core installation) |
6.2.9200.0
< 6.2.9200.26349
|
|
CVE-2026-69494 |
high
|
8.8 |
0.0082
|
Microsoft |
Windows Server 2012 R2 |
6.3.9600.0
< 6.3.9600.23398
|
|