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-70177 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70222 |
high | 7.8 | 0.0039 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70225 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70233 |
high | 7.8 | 0.0048 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70238 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70245 |
high | 7.8 | 0.0042 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70247 |
high | 7.8 | 0.0034 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70255 |
high | 7.8 | 0.0039 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70278 |
high | 7.8 | 0.0030 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70285 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70286 |
high | 7.8 | 0.0041 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70303 |
high | 7.8 | 0.0042 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-70566 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-73027 |
high | 7.8 | 0.0052 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-78459 |
high | 7.8 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-81969 |
high | 7.8 | 0.0034 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83499 |
high | 7.8 | 0.0034 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83506 |
high | 7.8 | 0.0040 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83508 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83513 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83514 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83567 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83569 |
high | 7.8 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83570 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83579 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83583 |
high | 7.8 | 0.0034 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83585 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83587 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83588 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83634 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83637 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83638 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83639 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83640 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83641 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83650 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83652 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83654 |
high | 7.8 | 0.0032 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83659 |
high | 7.8 | 0.0033 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83669 |
high | 7.8 | 0.0042 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83678 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83690 |
high | 7.8 | 0.0038 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83691 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83692 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83698 |
high | 7.8 | 0.0036 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83699 |
high | 7.8 | 0.0042 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83700 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83704 |
high | 7.8 | 0.0047 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83709 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 | |
CVE-2026-83712 |
high | 7.8 | 0.0035 | Microsoft | Windows Server 2022 | 10.0.20348.0 < 10.0.20348.5761 |