Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service
No fixed version listed yet.Check the vendor advisory. References ↓
Some HTTP/2 implementations, with no specific vendor or product identified, mishandle headers that have zero-length names and values (optionally Huffman-encoded), allocating memory for them and holding it until the session ends, which is an uncontrolled resource consumption flaw. An unauthenticated remote attacker with network access can send a stream of such headers without user interaction, consuming excess memory and potentially causing a denial of service.
Official description · CVE.org
Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 13 Aug 2019. No public exploit code or confirmed exploitation is recorded.
What security researchers reported
Not named in any threat report yetAlso mentioned in 4 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- clone school board5 Mar 2026
- clone school board5 Mar 2026
- recallsfschoolboard.org6 Dec 2023
- recallsfschoolboard.org19 Feb 2022