Compressed HTTP/3 requests can exhaust server memory: research urges checks of underlying packages
FoxIO found that some HTTP/3 components did not adequately limit decompressed data, allowing relatively small network requests to disrupt services. Several projects have issued fixes; website administrators should check the components actually in use.

Source Facts
FoxIO published QPACK research on 20 October, finding insufficient limits in 7 of 10 tested HTTP/3 implementations. QPACK compresses network data, but decompression on the server may consume excessive memory and cause denial of service.
The research focuses on service availability and does not establish data theft. The quic-go project lists version 0.57.0 as fixing the issue; Cloudflare quiche fixes it in 0.29.3. Impacts and versions differ by component, and the study's amplification factors cannot be applied to every website.
Some fixes predate this research article. For deployments not yet updated, operations staff should review official advisories, assess temporary restrictions on affected features and arrange compatibility testing.
A website opening normally does not mean its underlying communications components are updated. Inventory proxies, servers and the libraries they use together.
Original sources
- Header Accordions: QPACK amplification attacks against HTTP/3 servers ↗Published 2026.10.20
- HTTP/3 QPACK Header Expansion Memory Exhaustion ↗Published 2025.12.11
- Resource exhaustion in HTTP/3 and QPACK ↗Published 2026.07.14
Reporting leads · The Hacker News
The original material listed above has been traced. Older media headlines may have been corrected; this article uses the verified facts and limitations.
Header Accordions: QPACK amplification attacks against HTTP/3 servers
Sources checked: 2026-10-26 · Prepared with SI agent assistance; articles have not been individually reviewed by a person.
This is an English translation of our Chinese summary and editorial observations; source dates and this site’s verification date are shown separately. If an original advisory changes, refer to the source.


