CVE-2024-27316: Apache HTTP Server · Unthrottled Resource Allocation
Affects Apache HTTP ServerSource CVE Database V5
Not known to be exploited · 91% EPSS · CVSS 7.5 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 91.3% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Apacheapache/httpdpkg:rpm/apache/httpdOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade Apache HTTP Server to a version where this vulnerability is patched as soon as it becomes available from the Apache Software Foundation.
- In the interim, implement network-level rate limiting and filtering to detect and block clients sending excessive HTTP/2 headers.
- Employ Web Application Firewalls (WAFs) capable of inspecting HTTP/2 traffic and enforcing header size limits.
- Monitor server logs and network traffic for unusual spikes in HTTP/2 header sizes or repeated HTTP 413 responses, which may indicate exploitation attempts.
- Configure resource limits and timeouts in the HTTP/2 module or underlying nghttp2 library if configurable, to prevent excessive buffering.
- Conduct regular security assessments and penetration testing focusing on HTTP/2 protocol handling.
- Educate incident response teams to recognize symptoms of memory exhaustion and DoS conditions related to HTTP/2 traffic.
Description
HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.
References
- httpd.apache.org/security/vulnerabilities_24.html (opens in a new tab)
- openwall.com/lists/oss-security/2024/04/03/16 (opens in a new tab)
- openwall.com/lists/oss-security/2024/04/04/4 (opens in a new tab)
- support.apple.com/kb/HT214119 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Jul/18 (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/05/msg00013.html (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MIUBKSCJGPJ6M2U63V6BKFDF725ODLG7/ (opens in a new tab)
- security.netapp.com/advisory/ntap-20240415-0013/ (opens in a new tab)
- kb.cert.org/vuls/id/421644 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FO73U3SLBYFGIW2YKXOK7RI4D6DJSZ2B/ (opens in a new tab)