← All stories
● Covered by 1 source · 1 reportMedium impact1 negative

New QPACK Flaws Allow Remote HTTP/3 Server Crashes and Memory Amplification

🔄 Updated 16d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • Unauthenticated remote attackers can crash HTTP/3 servers.
  • Flaws cause denial-of-service via memory amplification.
  • Affected stacks fail to cap unpacked header size during QPACK decoding.
  • Fixes are available for some stacks, others remain unpatched.

Discovery of QPACK Vulnerabilities

Security firm FoxIO has revealed critical flaws in the QPACK compression scheme used by HTTP/3, enabling remote, unauthenticated attackers to trigger denial-of-service attacks. The firm released proof-of-concept code demonstrating how a single connection can crash vulnerable HTTP/3 web servers.

Mechanism of Attack

The vulnerabilities stem from how HTTP/3 stacks handle compressed HTTP headers. Attackers send a small batch of compressed headers that, when unpacked, expand into a much larger data set, forcing the server to consume significantly more memory than received. This memory amplification can reach up to 4,000 times the original input, leading to out-of-memory conditions and server crashes.

The core issue lies in the QPACK implementation, where affected stacks either fail to cap the size of unpacked headers or apply the cap too late in the decoding process. This allows a single request to generate hundreds of thousands of header entries held in server memory.

Affected Systems and Patches

FoxIO identified these flaws in seven out of ten HTTP/3 stacks tested. Patches have been released for quic-go, Cloudflare quiche, lsquic, and Wireshark. However, Bun, the h3 Rust library, and aioquic remained unpatched at the time of disclosure. IIS, Envoy, ngtcp2/nghttp3, and Google's quiche were not affected due to proper header capping during decoding.

The impact is broad, as these vulnerable stacks underpin common software. For example, quic-go is used by Caddy, Traefik, and cloudflared, while lsquic is integral to LiteSpeed Web Server, OpenLiteSpeed, and Bun's HTTP/3 server.

Attack Vector and Impact

Attackers do not require an account or special access to exploit these vulnerabilities. Since HTTP/3 operates over UDP, requests can reach the server before many standard filtering mechanisms are applied. The attacks are limited to denial-of-service, with no evidence of data theft or code execution, and no public reports of in-the-wild exploitation.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

Security firm FoxIO disclosed vulnerabilities in HTTP/3 QPACK implementations that allow unauthenticated remote attackers to crash servers via denial-of-service attacks. These flaws enable memory amplification up to 4,000-fold by sending compressed HTTP headers that expand significantly upon unpacking, affecting multiple widely used HTTP/3 stacks.