Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY135 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.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
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 ↗
CVE-2023-38709 4 Apr 2024 ≤ 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-2023-31122 23 Oct 2023 ≤ 2.4.57 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-2023-43622 23 Oct 2023 2.4.55 ≤ 2.4.57 2.4.58 Update reference ↗
CVE-2023-45802 23 Oct 2023 2.4.17 ≤ 2.4.57 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-2023-27522 7 Mar 2023 2.4.30 ≤ 2.4.55 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-2023-25690 7 Mar 2023 2.4.0 ≤ 2.4.55 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-37436 17 Jan 2023 < 2.4.55 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-2022-36760 17 Jan 2023 2.4 ≤ 2.4.54 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-2006-20001 17 Jan 2023 2.4 ≤ 2.4.54 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-31813 8 Jun 2022 Apache HTTP Server 2.4 ≤ 2.4.53 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-30556 8 Jun 2022 unspecified ≤ 2.4.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-30522 8 Jun 2022 2.4.53 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-29404 8 Jun 2022 unspecified ≤ 2.4.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28615 8 Jun 2022 Apache HTTP Server ≤ 2.4.53 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-28614 8 Jun 2022 unspecified ≤ 2.4.53 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-28330 8 Jun 2022 Apache HTTP Server ≤ 2.4.53 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-26377 8 Jun 2022 Apache HTTP Server 2.4 ≤ 2.4.53 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-23943 14 Mar 2022 2.4 ≤ 2.4.52 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-22721 14 Mar 2022 Apache HTTP Server 2.4 ≤ 2.4.52 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-22720 14 Mar 2022 Apache HTTP Server 2.4 ≤ 2.4.52 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2022-22719 14 Mar 2022 Apache HTTP Server 2.4 ≤ 2.4.52 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-2021-44224 20 Dec 2021 2.4.7 < Apache HTTP Server 2.4* For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2021-44790 20 Dec 2021 Apache HTTP Server 2.4 ≤ 2.4.51 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-2021-41524 5 Oct 2021 2.4.49 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2021-39275 16 Sep 2021 Apache HTTP Server 2.4 ≤ 2.4.48 Update to V1.0.3 or later version Update reference ↗
CVE-2021-36160 16 Sep 2021 Apache HTTP Server 2.4 ≤ 2.4.48 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2021-34798 16 Sep 2021 Apache HTTP Server 2.4 ≤ 2.4.48 Update to V1.0.3 or later version Update reference ↗
CVE-2021-33193 16 Aug 2021 Apache HTTP Server 2.4 2.4.17 to 2.4.48 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Applications using the APR libraries, such as httpd, must be restarted for this update to take effect. After installing the updated packages, the httpd daemon will be restarted automatically. Update reference ↗
CVE-2021-31618 15 Jun 2021 2.4.47 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-2021-30641 10 Jun 2021 2.4.46; 2.4.43; 2.4.41; 2.4.39 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.