Affected Software Search
Search CVEs by vendor or product name from CPE data.
1,650 CVEs matching "windows_server_2022"
| CVE | Severity | CVSS | EPSS | Vendor | Product | Version | Flags |
|---|---|---|---|---|---|---|---|
CVE-2026-70133 |
high | 7.5 | 0.0127 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70155 |
high | 7.5 | 0.0133 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70163 |
high | 7.5 | 0.0123 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70207 |
high | 7.5 | 0.0075 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83515 |
high | 7.5 | 0.0107 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83516 |
high | 7.5 | 0.0136 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83635 |
high | 7.5 | 0.0133 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83645 |
high | 7.5 | 0.0125 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83647 |
high | 7.5 | 0.0130 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83651 |
high | 7.5 | 0.0107 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83655 |
high | 7.5 | 0.0136 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83665 |
high | 7.5 | 0.0136 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83670 |
high | 7.5 | 0.0109 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83739 |
high | 7.5 | 0.0048 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83754 |
high | 7.5 | 0.0068 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83795 |
high | 7.5 | 0.0127 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83843 |
high | 7.5 | 0.0127 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83856 |
high | 7.5 | 0.0063 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83860 |
high | 7.5 | 0.0127 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-84017 |
high | 7.5 | 0.0112 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85319 |
high | 7.5 | 0.0110 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85321 |
high | 7.5 | 0.0106 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85322 |
high | 7.5 | 0.0103 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85324 |
high | 7.5 | 0.0075 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85334 |
high | 7.5 | 0.0098 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85353 |
high | 7.5 | 0.0098 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85808 |
high | 7.5 | 0.0112 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85811 |
high | 7.5 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-87713 |
high | 7.5 | 0.0027 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-87716 |
high | 7.5 | 0.0112 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96245 |
high | 7.5 | 0.0098 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96246 |
high | 7.5 | 0.0098 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96248 |
high | 7.5 | 0.0112 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96861 |
high | 7.5 | 0.0112 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96866 |
high | 7.5 | 0.0112 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-97789 |
high | 7.5 | 0.0056 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-26154 |
high | 7.5 | 0.0106 | microsoft | windows_server_2022 | < 10.0.20348.5020 | |
CVE-2026-26154 |
high | 7.5 | 0.0106 | microsoft | windows_server_2022_23h2 | < 10.0.25398.2274 | |
CVE-2026-32071 |
high | 7.5 | 0.0106 | microsoft | windows_server_2022 | < 10.0.20348.5020 | |
CVE-2026-32071 |
high | 7.5 | 0.0106 | microsoft | windows_server_2022_23h2 | < 10.0.25398.2274 | |
CVE-2026-40378 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-49171 |
high | 7.5 | 0.0030 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-49181 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-49787 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-49788 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-50695 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-50696 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-54119 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-54983 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-50304 |
high | 7.5 | 0.0117 | microsoft | windows_server_2022 | < 10.0.20348.5386 |