← Search results
CVE-LINKED INVENTORY115 SECURITY RECORDS
Apache Software Foundation
Apache HTTP Server
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-49975 | 8 Jun 2026 | 2.4.17 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-48913 | 8 Jun 2026 | 2.4.55 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-42536 | 8 Jun 2026 | Apache HTTP Server: 2.4.0 ≤ 2.4.67 | RHSA-2026:56868: Red Hat JBoss Core Services on RHEL 8 | Update reference ↗ |
| CVE-2026-44185 | 8 Jun 2026 | Apache HTTP Server: 2.4.0 ≤ 2.4.67 | RHSA-2026:56868: Red Hat JBoss Core Services on RHEL 8 | Update reference ↗ |
| CVE-2026-34355 | 8 Jun 2026 | Apache HTTP Server: 2.4.0 ≤ 2.4.67 | RHSA-2026:56868: Red Hat JBoss Core Services on RHEL 8 | Update reference ↗ |
| CVE-2026-44631 | 8 Jun 2026 | 2.4.0 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-44119 | 8 Jun 2026 | 2.4.0 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-43951 | 8 Jun 2026 | 2.4.0 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-42535 | 8 Jun 2026 | ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-34356 | 8 Jun 2026 | 2.4.0 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-44186 | 8 Jun 2026 | 2.4.0 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-29170 | 8 Jun 2026 | ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-29167 | 8 Jun 2026 | 2.4.0 ≤ 2.4.67 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-28780 | 5 May 2026 | Apache HTTP Server: ≤ 2.4.66 | RHSA-2026:27200: Red Hat JBoss Core Services on RHEL 7 Server, Red Hat JBoss Core Services on RHEL 8 | Update reference ↗ |
| CVE-2026-29168 | 5 May 2026 | 2.4.30 ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-29169 | 4 May 2026 | ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-23918 | 4 May 2026 | 2.4.66 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33006 | 4 May 2026 | ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-33007 | 4 May 2026 | 2.4.0 ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-33523 | 4 May 2026 | 2.4.0 ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-33857 | 4 May 2026 | ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-34032 | 4 May 2026 | ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-34059 | 4 May 2026 | ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-24072 | 4 May 2026 | ≤ 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-58098 | 5 Dec 2025 | Apache HTTP Server: < 2.4.66 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-66200 | 5 Dec 2025 | 2.4.7 ≤ 2.4.65 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-65082 | 5 Dec 2025 | Apache HTTP Server: 2.4.0 ≤ 2.4.65 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-59775 | 5 Dec 2025 | Apache HTTP Server: 2.4.0 ≤ 2.4.65 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-55753 | 5 Dec 2025 | 2.4.30 < 2.4.66 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-54090 | 23 Jul 2025 | 2.4.64 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-53020 | 10 Jul 2025 | 2.4.17 ≤ 2.4.63 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-49812 | 10 Jul 2025 | ≤ 2.4.63 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-49630 | 10 Jul 2025 | 2.4.26 ≤ 2.4.63 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-23048 | 10 Jul 2025 | 2.4.35 ≤ 2.4.63 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-43394 | 10 Jul 2025 | 2.4.0 ≤ 2.4.63 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-47252 | 10 Jul 2025 | 2.4 ≤ 2.4.63 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-43204 | 10 Jul 2025 | 2.4.0 ≤ 2.4.63 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-42516 | 10 Jul 2025 | 2.4.0 ≤ 2.4.63 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-40725 | 18 Jul 2024 | 2.4.60 ≤ 2.4.61 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-40898 | 18 Jul 2024 | 2.4.0 ≤ 2.4.61 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-39884 | 4 Jul 2024 | 2.4.60 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-39573 | 1 Jul 2024 | 2.4.0 ≤ 2.4.59 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-38477 | 1 Jul 2024 | 2.4.0 ≤ 2.4.59 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-38476 | 1 Jul 2024 | 2.4.0 ≤ 2.4.59 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-38474 | 1 Jul 2024 | 2.4.0 ≤ 2.4.59 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-38473 | 1 Jul 2024 | 2.4.0 ≤ 2.4.59 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-38472 | 1 Jul 2024 | 2.4.0 ≤ 2.4.59 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-36387 | 1 Jul 2024 | 2.4.55 ≤ 2.4.59 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-27316 | 4 Apr 2024 | 2.4.17 ≤ 2.4.58 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2024-24795 | 4 Apr 2024 | 2.4.0 ≤ 2.4.58 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.