News KrakenD 3.0 Is Here: AI Router, Semantic Cache, and On-the-Fly Stream Manipulation News CVE-2026-98432: Linux Kernel Flaw Exposing KrakenD on Unpatched Hosts News KrakenD Partners with Aice Global to Deliver Secure API Management in India News KrakenD CE 3.0.2, EE 3.0.2 and EE 2.13.12 Update Released

CVE-2026-40898 CVE High · CVSS 7.5 False Positive

quic-go: HTTP/3 Memory Exhaustion via Unbounded QPACK Trailer Decompression

This advisory does not affect KrakenD

KrakenD bundles the vulnerable quic-go library only transitively: gin imports quic-go/http3 at the package level to expose its RunQUIC() helper. KrakenD never calls RunQUIC(): it serves traffic over standard net/http (HTTP/1.1 and HTTP/2) and uses no HTTP/3 client to reach backends. With no HTTP/3 server started and no HTTP/3 client in use, the vulnerable QPACK trailer-decoding path is never executed, and there is no configuration option that enables HTTP/3 serving. SCA scanners may flag quic-go in the binary, but reachability-aware tools such as govulncheck correctly report it as not affected.

Addressed through routine dependency maintenance in CE 2.13.8 and EE 2.13.6.

Component

quic-go (HTTP/3)

Disclosed

Jun 17, 2026

CVSS Score

7.5

Description

The quic-go QUIC/HTTP-3 library limits the size of the QPACK-compressed HEADERS frame but not the size of the decoded field section. A malicious peer can send crafted QPACK-encoded HEADERS frames whose trailers decompress into an enormous http.Header, exhausting memory and causing a denial of service on both HTTP/3 servers and clients. The flaw was fixed in quic-go v0.59.1, which enforces the RFC 9114 field section size limit with incremental validation.

Stay up to date with KrakenD releases and important updates