Unauthenticated service interruption via unbounded header buffering
Published Apr 4, 2024 · Updated Nov 4, 2025
HTTP/2 handling in Apache HTTP Server 2.4.17 through 2.4.58 allows remote attackers to exhaust memory via endless header frames. After the header limit is exceeded, the request path keeps buffering incoming CONTINUATION frames in nghttp2 while preparing an HTTP 413 response. An unauthenticated client with HTTP/2 access can keep a request open until the server runs out of memory and service is interrupted.
Summary
What happened
HTTP/2 handling in Apache HTTP Server 2.4.17 through 2.4.58 allows remote attackers to exhaust memory via endless header frames. After the header limit is exceeded, the request path keeps buffering incoming CONTINUATION frames in nghttp2 while preparing an HTTP 413 response. An unauthenticated client with HTTP/2 access can keep a request open until the server runs out of memory and service is interrupted.
The record
- CVE
- CVE-2024-27316
- Published
- Apr 4, 2024
- Updated
- Nov 4, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache HTTP Server
- Classifications
- CWE-770, T1499.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.4.17 <=2.4.58
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo