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-85806 |
critical | 9.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85809 |
critical | 9.8 | 0.0093 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85814 |
critical | 9.8 | 0.0093 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85928 |
critical | 9.8 | 0.0065 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88102 |
critical | 9.8 | 0.0063 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96096 |
critical | 9.8 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96219 |
critical | 9.8 | 0.0089 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96864 |
critical | 9.8 | 0.0065 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-50380 |
critical | 9.6 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-49798 |
critical | 9.3 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-96252 |
critical | 9.1 | 0.0056 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-105008 |
critical | 9.0 | 0.0066 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-85818 |
critical | 9.0 | 0.0041 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-62790 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62822 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62823 |
high | 8.8 | 0.0053 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-48564 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-49178 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-49179 |
high | 8.8 | 0.0086 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | 1 PoC |
CVE-2026-49795 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50360 |
high | 8.8 | 0.0078 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50369 |
high | 8.8 | 0.0070 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | 1 PoC |
CVE-2026-50370 |
high | 8.8 | 0.0050 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50382 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50444 |
high | 8.8 | 0.0078 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50474 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50477 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50489 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50666 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50670 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-50692 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-54107 |
high | 8.8 | 0.0021 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-54121 |
high | 8.8 | 0.0078 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | 15 PoC |
CVE-2026-54982 |
high | 8.8 | 0.0053 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-54999 |
high | 8.8 | 0.0041 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-56194 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-56647 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-57087 |
high | 8.8 | 0.0079 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-57090 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-57094 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-58534 |
high | 8.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-58594 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-58608 |
high | 8.8 | 0.0057 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-58626 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5386 | |
CVE-2026-62784 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62785 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62795 |
high | 8.8 | 0.0082 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62816 |
high | 8.8 | 0.0053 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62817 |
high | 8.8 | 0.0053 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62818 |
high | 8.8 | 0.0091 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 |