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-83740 |
high | 7.0 | 0.0028 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-70198 |
high | 7.0 | 0.0030 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-83666 |
high | 7.0 | 0.0022 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-83694 |
high | 7.0 | 0.0028 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-83722 |
high | 7.0 | 0.0023 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-83696 |
high | 7.0 | 0.0029 | microsoft | windows_server_2022 | < 10.0.20348.5761 | |
CVE-2026-59122 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-59125 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-59126 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-61348 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-61366 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-61939 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62690 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62723 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62724 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62725 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62726 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62727 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62728 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62729 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62734 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62748 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62753 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62773 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62774 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62892 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62908 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65678 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-68820 |
high | 7.0 | 0.0857 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | KEV 4 PoC |
CVE-2026-70307 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-50472 |
high | 7.0 | 0.0026 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-100201 |
high | 7.0 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-100203 |
high | 7.0 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-100216 |
high | 7.0 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-100225 |
high | 7.0 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102189 |
high | 7.0 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102191 |
high | 7.0 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102194 |
high | 7.0 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102207 |
high | 7.0 | 0.0022 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102208 |
high | 7.0 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102211 |
high | 7.0 | 0.0023 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-103555 |
high | 7.0 | 0.0028 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-108132 |
high | 7.0 | 0.0028 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-108396 |
high | 7.0 | 0.0021 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-109453 |
high | 7.0 | 0.0028 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69915 |
high | 7.0 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70160 |
high | 7.0 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88141 |
high | 7.0 | 0.0025 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88149 |
high | 7.0 | 0.0020 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96209 |
high | 7.0 | 0.0028 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 |