Koffei

CVE-2025-64702

🟠 Medium

quic-go (HTTP/3 client and server; embedded in Caddy, Traefik and cloudflared) · < 0.57.0 (the advisory states ≤ 0.56.0)

CVSS (Koffei note)
5.3
CVSS (v3.1, CVE List)
5.3
EPSS (2026-11-18)
0.983%
62.98th percentile

Exploitation

Probable — public PoC (FoxIO) ; no in-the-wild exploitation found (SSVC: none) ; not in KEV

Timeline

  1. 11/12/2025CVE record published (CVE List)
  2. 23/10/2026QPACK amplification research against HTTP/3 servers

Risk

5.3 Medium (v3.1, GitHub CNA) — AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, EPSS 0.364% (CWE-770 : the HTTP/3 client and server limit only the QPACK-compressed HEADERS frame, not the decoded field section, so a small frame decompresses into many unique header names and is retained in an http.Header, exhausting memory — a QPACK amplification denial of service)

Fix

Yes — 0.57.0 (GHSA-g754-hx8w-x2g6) — MaxHeaderBytes and MaxResponseHeaderBytes do not mitigate this: they cap only the encoded frame

Official description

quic-go is an implementation of the QUIC protocol in Go. Versions 0.56.0 and below are vulnerable to excessive memory allocation through quic-go's HTTP/3 client and server implementations by sending a QPACK-encoded HEADERS frame that decodes into a large header field section (many unique header names and/or large values). The implementation builds an http.Header (used on the http.Request and http.Response, respectively), while only enforcing limits on the size of the (QPACK-compressed) HEADERS frame, but not on the decoded header, leading to memory exhaustion. This issue is fixed in version 0.57.0.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CWE-770