Affected Software Search
Search CVEs by vendor or product name from CPE data.
1,488 CVEs matching "Windows Server 2022"
| CVE | Severity | CVSS | EPSS | Vendor | Product | Version | Flags |
|---|---|---|---|---|---|---|---|
CVE-2026-100220 |
high | 8.8 | 0.0093 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102203 |
high | 8.8 | 0.0085 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102214 |
high | 8.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102217 |
high | 8.8 | 0.0126 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102225 |
high | 8.8 | 0.0089 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-103575 |
high | 8.8 | 0.0085 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-105007 |
high | 8.8 | 0.0085 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88112 |
high | 8.8 | 0.0070 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88114 |
high | 8.8 | 0.0070 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88116 |
high | 8.8 | 0.0072 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88219 |
high | 8.8 | 0.0085 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96913 |
high | 8.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96914 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96917 |
high | 8.8 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96952 |
high | 8.8 | 0.0090 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-105733 |
high | 8.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-108458 |
high | 8.8 | 0.0085 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-108467 |
high | 8.8 | 0.0100 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69326 |
high | 8.8 | 0.0077 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69521 |
high | 8.8 | 0.0080 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69918 |
high | 8.8 | 0.0041 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69945 |
high | 8.8 | 0.0032 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69985 |
high | 8.8 | 0.0080 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70068 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70069 |
high | 8.8 | 0.0103 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70089 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70149 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70158 |
high | 8.8 | 0.0096 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70167 |
high | 8.8 | 0.0098 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70185 |
high | 8.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70210 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70250 |
high | 8.8 | 0.0048 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70258 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70262 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70275 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70580 |
high | 8.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-77496 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83642 |
high | 8.8 | 0.0093 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83643 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83688 |
high | 8.8 | 0.0095 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83716 |
high | 8.8 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83725 |
high | 8.8 | 0.0078 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83728 |
high | 8.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83759 |
high | 8.8 | 0.0092 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83771 |
high | 8.8 | 0.0062 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83777 |
high | 8.8 | 0.0062 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83778 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83784 |
high | 8.8 | 0.0108 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83789 |
high | 8.8 | 0.0087 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83797 |
high | 8.8 | 0.0085 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 |