Bug 2379343 (CVE-2025-53020) - CVE-2025-53020 mod_http2: Apache HTTP Server: HTTP/2 DoS by Memory Increase
Summary: CVE-2025-53020 mod_http2: Apache HTTP Server: HTTP/2 DoS by Memory Increase
Keywords:
Status: NEW
Alias: CVE-2025-53020
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2379347 2379348
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-10 18:01 UTC by OSIDB Bzimport
Modified: 2026-06-03 04:37 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github apache/httpd/commit/a6b8db04ec2436d6fe5ef7ac70211a02b454113b 0 None None None 2026-05-05 17:40:36 UTC
Red Hat Product Errata RHSA-2026:22140 0 None None None 2026-06-01 02:26:24 UTC
Red Hat Product Errata RHSA-2026:22528 0 None None None 2026-06-03 04:37:03 UTC
Red Hat Product Errata RHSA-2026:22551 0 None None None 2026-06-03 04:37:17 UTC

Description OSIDB Bzimport 2025-07-10 18:01:11 UTC 
Late Release of Memory after Effective Lifetime vulnerability in Apache HTTP Server.

This issue affects Apache HTTP Server: from 2.4.17 up to 2.4.63.

Users are recommended to upgrade to version 2.4.64, which fixes the issue.
Comment 3 errata-xmlrpc 2026-06-01 02:26:22 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:22140 https://access.redhat.com/errata/RHSA-2026:22140
Comment 4 errata-xmlrpc 2026-06-03 04:37:01 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:22528 https://access.redhat.com/errata/RHSA-2026:22528
Comment 5 errata-xmlrpc 2026-06-03 04:37:15 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:22551 https://access.redhat.com/errata/RHSA-2026:22551
Note You need to log in before you can comment on or make changes to this bug.