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-62719 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62721 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62732 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62733 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62735 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | 2 PoC |
CVE-2026-62739 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62741 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62747 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62751 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62754 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62755 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62758 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62768 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62770 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62771 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62776 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62777 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62783 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62797 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62803 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62807 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62811 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62812 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62876 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62880 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62885 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62888 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62890 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-62894 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65671 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65672 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65773 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65774 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65786 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65787 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65790 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-65814 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-66799 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-70345 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-70346 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-70347 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-56174 |
high | 7.8 | 0.0046 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5499 | |
CVE-2026-100215 |
high | 7.8 | 0.0055 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-100217 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102202 |
high | 7.8 | 0.0041 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102205 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102215 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102216 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102218 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102220 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 |