| RHSA-2026:55992 |
2026-08-18 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-53020, CVE-2026-43951, CVE-2026-48913, CVE-2026-49975 |
mod_http2 security update |
| RHSA-2026:55930 |
2026-08-18 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-53020, CVE-2026-43951, CVE-2026-49975 |
mod_http2 security update |
| RHSA-2026:50572 |
2026-08-05 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2025-53020, CVE-2026-43951, CVE-2026-48913, CVE-2026-49975 |
mod_http2 security update |
| RHSA-2026:50538 |
2026-08-05 |
Important |
Apache (httpd 2.4) |
10 |
CVE-2025-53020, CVE-2026-43951, CVE-2026-48913, CVE-2026-49975 |
mod_http2 security update |
| RHSA-2026:36846 |
2026-07-08 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-53020, CVE-2026-28780, CVE-2026-33007, CVE-2026-33857, CVE-2026-34032, CVE-2026-34059, CVE-2026-49975 |
httpd:2.4 security update |
| RHSA-2026:36831 |
2026-07-08 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-53020, CVE-2026-28780, CVE-2026-33007, CVE-2026-33857, CVE-2026-34032, CVE-2026-34059, CVE-2026-49975 |
httpd:2.4 security update |
| RHSA-2026:36373 |
2026-07-07 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2025-53020, CVE-2026-28780, CVE-2026-33007, CVE-2026-33857, CVE-2026-34032, CVE-2026-34059, CVE-2026-49975 |
httpd:2.4 security update |
| RHSA-2026:25225 |
2026-06-11 |
Important |
Apache (httpd 2.4) |
10 |
CVE-2026-49975 |
mod_http2 security update |
| RHSA-2026:25090 |
2026-06-10 |
Important |
Apache (httpd 2.4) |
8 |
CVE-2026-49975 |
httpd:2.4 security update |
| RHSA-2026:25057 |
2026-06-10 |
Important |
Apache (httpd 2.4) |
9 |
CVE-2026-49975 |
mod_http2 security update |