Quick answers
- Is CVE-2026-40898 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40898 being exploited in the wild.
- How severe is CVE-2026-40898?
- Medium severity, with a CVSS score of 5.3, published 4 June 2026.
- Which products and versions are affected?
- github.com/quic-go/quic-go (Go) <= 0.59.0, SEMVER:introduced=0,fixed=0.59.1; Quic-Go <= 0.59.0, <= v0.59.0.
- Is there a fix for CVE-2026-40898?
- Yes. github.com/quic-go/quic-go (Go): upgrade to 0.59.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40898 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-40898?
- Check whether you run github.com/quic-go/quic-go (Go) or Quic-Go at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/quic-go/quic-go (Go): upgrade to 0.59.1 or later
go get github.com/quic-go/quic-go@v0.59.1
Technical details
A resource exhaustion vulnerability exists in quic-go's HTTP/3 implementation due to improper validation of decoded field section sizes in QPACK-encoded HEADERS frames used for trailers. While the library enforced limits on the size of compressed frames, it failed to limit the size of the decoded field section. An attacker can exploit this by sending a crafted HEADERS frame that expands significantly upon decoding (up to 50x), leading to excessive memory allocation in both client and server implementations. This issue is addressed in version 0.59.1 by implementing incremental decoding and enforcing RFC 9114 size limits for trailers.
Affected products
- quic-go quic-go <= v0.59.0
Identifiers
- CVE-2026-40898
- GHSA-vvgj-x9jq-8cj9
- GO-2026-5676
Timeline
- 2026-05-11: patched: Version 0.59.1 released
- 2026-05-31: advisory: GitHub Security Advisory published
- 2026-06-04: disclosed: CVE-2026-40898 published to NVD