QPACK Flaws

QPACK

QPACK flaws can crash HTTP/3 servers, trigger memory amplification

Do this now

Disable HTTP/3 on servers exposed to untrusted clients until QPACK fixes are available.

First seen: 22 Oct 2026
Last update: 22 Oct 2026, 06:38 UTC
Source: news
On the menu as: nginx

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## QPACK Flaws
Severity: unknown. Patch status: no fix yet.
Affected: QPACK

QPACK flaws can crash HTTP/3 servers, trigger memory amplification

## Steps
1. This touches infrastructure (nginx). Look in terraform, ansible, cloud-init, Dockerfiles and docs for the product and version we run. If it isn't in the repo, say so and list what a human should check on the box.
2. There is no fix yet. Until one ships: QPACK flaws can crash HTTP/3 servers, trigger memory amplification

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://thehackernews.com/2026/10/new-qpack-flaws-can-crash-http3-servers.html
https://pwned.coffee/i/qpack-flaws

Receipt

Exploitation: No known exploitation
Score: No CVSS published yet: severity unknown.
Last checked: 24 Oct 2026, 17:17 UTC

Sources: KEV – CVE record – Vendor –

Sources

feeds.feedburner.com: New QPACK Flaws Can Crash HTTP/3 Servers, Trigger Up to 4,000-Fold Memory Amplification

Totalone coffee