| RHSA-2026:0171 |
2026-01-06 |
Important |
Apache (httpd 2.4) |
10 |
CVE-2025-58098 |
httpd security update |
| RHSA-2026:0141 |
2026-01-06 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-58098 |
httpd security update |
| RHSA-2026:0139 |
2026-01-06 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-58098 |
httpd security update |
| RHSA-2026:0095 |
2026-01-06 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-58098 |
httpd security update |
| RHSA-2026:0090 |
2026-01-06 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-58098 |
httpd security update |
| RHSA-2026:0012 |
2026-01-05 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-55753, CVE-2025-58098 |
httpd:2.4 security update |
| RHSA-2026:0011 |
2026-01-05 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-55753, CVE-2025-58098 |
httpd:2.4 security update |
| RHSA-2026:0010 |
2026-01-05 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-55753, CVE-2025-58098 |
httpd:2.4 security update |
| RHSA-2026:0009 |
2026-01-05 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-55753, CVE-2025-58098 |
httpd:2.4 security update |
| RHSA-2025:23932 |
2025-12-22 |
Important |
Apache (httpd 2.4) |
10 |
CVE-2025-58098, CVE-2025-65082, CVE-2025-66200 |
httpd security update |
| RHSA-2025:23919 |
2025-12-22 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-58098, CVE-2025-65082, CVE-2025-66200 |
httpd security update |
| RHSA-2025:23732 |
2025-12-22 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-55753, CVE-2025-58098, CVE-2025-65082, CVE-2025-66200 |
httpd:2.4 security update |