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-103553 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-103568 |
high | 7.8 | 0.0021 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-105003 |
high | 7.8 | 0.0034 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-105004 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-108136 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69884 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70023 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70054 |
high | 7.8 | 0.0046 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70112 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70143 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70228 |
high | 7.8 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88093 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88133 |
high | 7.8 | 0.0054 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88177 |
high | 7.8 | 0.0024 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88179 |
high | 7.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88180 |
high | 7.8 | 0.0024 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88181 |
high | 7.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88182 |
high | 7.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88188 |
high | 7.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88189 |
high | 7.8 | 0.0024 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88191 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88193 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-88194 |
high | 7.8 | 0.0031 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96118 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96186 |
high | 7.8 | 0.0240 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96243 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96324 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96843 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96847 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96911 |
high | 7.8 | 0.0055 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96912 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96915 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96916 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96918 |
high | 7.8 | 0.0032 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96929 |
high | 7.8 | 0.0048 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96931 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96933 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96946 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96947 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96950 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-96953 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-97792 |
high | 7.8 | 0.0032 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-97798 |
high | 7.8 | 0.0037 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | 2 PoC |
CVE-2026-97804 |
high | 7.8 | 0.0034 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-97811 |
high | 7.8 | 0.0029 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-102227 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-49785 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-68836 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-69354 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5622 | |
CVE-2026-69471 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 |