| CVE-2024-38475 CRITICAL 9.1 known exploited |
http_server 2.4.52 · port 80 |
| CVE-2022-22720 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2022-23943 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2022-31813 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2023-25690 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2024-38474 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2024-38476 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2026-28780 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2026-29167 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2026-44631 CRITICAL 9.8 |
http_server 2.4.52 · port 80 |
| CVE-2022-22721 CRITICAL 9.1 |
http_server 2.4.52 · port 80 |
| CVE-2022-28615 CRITICAL 9.1 |
http_server 2.4.52 · port 80 |
| CVE-2025-23048 CRITICAL 9.1 |
http_server 2.4.52 · port 80 |
| CVE-2026-42535 CRITICAL 9.1 |
http_server 2.4.52 · port 80 |
| CVE-2022-36760 CRITICAL 9.0 |
http_server 2.4.52 · port 80 |
| CVE-2026-24072 HIGH 8.8 |
http_server 2.4.52 · port 80 |
| CVE-2025-58098 HIGH 8.3 |
http_server 2.4.52 · port 80 |
| CVE-2024-38473 HIGH 8.1 |
http_server 2.4.52 · port 80 |
| CVE-2006-20001 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2022-22719 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2022-26377 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2022-29404 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2022-30556 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2023-27522 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2023-31122 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-27316 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-38472 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-38477 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-39573 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-42516 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-43204 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-47252 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2025-49630 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2025-53020 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2025-55753 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2025-59775 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-29169 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-34059 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-34355 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-34356 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-42536 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-49975 HIGH 7.5 |
http_server 2.4.52 · port 80 |
| CVE-2025-49812 HIGH 7.4 |
http_server 2.4.52 · port 80 |
| CVE-2023-38709 HIGH 7.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-29168 HIGH 7.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-44185 HIGH 7.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-44186 HIGH 7.3 |
http_server 2.4.52 · port 80 |
| CVE-2025-65082 MEDIUM 6.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-33523 MEDIUM 6.5 |
http_server 2.4.52 · port 80 |
| CVE-2026-43951 MEDIUM 6.5 |
http_server 2.4.52 · port 80 |
| CVE-2024-24795 MEDIUM 6.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-29170 MEDIUM 6.1 |
http_server 2.4.52 · port 80 |
| CVE-2023-45802 MEDIUM 5.9 |
http_server 2.4.52 · port 80 |
| CVE-2026-44119 MEDIUM 5.5 |
http_server 2.4.52 · port 80 |
| CVE-2025-66200 MEDIUM 5.4 |
http_server 2.4.52 · port 80 |
| CVE-2022-28614 MEDIUM 5.3 |
http_server 2.4.52 · port 80 |
| CVE-2022-37436 MEDIUM 5.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-33007 MEDIUM 5.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-33857 MEDIUM 5.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-34032 MEDIUM 5.3 |
http_server 2.4.52 · port 80 |
| CVE-2026-33006 MEDIUM 4.8 |
http_server 2.4.52 · port 80 |