Affected Software Search
Search CVEs by vendor or product name from CPE data.
2,267 CVEs matching "windows_server_2022"
| CVE | Severity | CVSS | EPSS | Vendor | Product | Version | Flags |
|---|---|---|---|---|---|---|---|
CVE-2026-62813 |
high | 7.5 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-68887 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69429 |
high | 7.5 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69443 |
high | 7.5 | 0.0103 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69514 |
high | 7.5 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69539 |
high | 7.5 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69587 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69588 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69631 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69890 |
high | 7.5 | 0.0028 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-70065 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-70587 |
high | 7.5 | 0.0103 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-71330 |
high | 7.5 | 0.0103 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-72943 |
high | 7.5 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-72949 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77494 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77498 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77499 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77501 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77502 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77886 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77888 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77889 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77890 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77893 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-77895 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-81355 |
high | 7.5 | 0.0027 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-84001 |
high | 7.5 | 0.0117 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-83511 |
high | 7.4 | 0.0065 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-87705 |
high | 7.4 | 0.0043 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-32156 |
high | 7.4 | 0.0029 | microsoft | windows_server_2022 | < 10.0.20348.5020 | |
CVE-2026-32156 |
high | 7.4 | 0.0029 | microsoft | windows_server_2022_23h2 | < 10.0.25398.2274 | |
CVE-2026-54127 |
high | 7.4 | 0.0031 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-96222 |
high | 7.4 | 0.0059 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-83511 |
high | 7.4 | 0.0065 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-87705 |
high | 7.4 | 0.0043 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96222 |
high | 7.4 | 0.0059 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69347 |
high | 7.4 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-32149 |
high | 7.3 | 0.0032 | microsoft | windows_server_2022 | < 10.0.20348.5020 | |
CVE-2026-32149 |
high | 7.3 | 0.0032 | microsoft | windows_server_2022_23h2 | < 10.0.25398.2274 | |
CVE-2026-49789 |
high | 7.3 | 0.0036 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-49790 |
high | 7.3 | 0.0036 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-58640 |
high | 7.3 | 0.0036 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-50482 |
high | 7.3 | 0.0036 | microsoft | windows_server_2022 | < 10.0.20348.5386 | |
CVE-2026-108399 |
high | 7.2 | 0.0038 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-85798 |
high | 7.2 | 0.0087 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-108399 |
high | 7.2 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85798 |
high | 7.2 | 0.0087 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70126 |
high | 7.1 | 0.0052 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-26151 |
high | 7.1 | 0.0083 | microsoft | windows_server_2022 | < 10.0.20348.5020 |