CVE-2026-40898

quic-go: HTTP/3 QPACK Trailer Expansion Memory Exhaustion

HIGH
7.5
CVSS Score
Published: June 4, 2026 at 05:43 PM UTC
Updated: July 22, 2026 at 08:24 PM UTC
2 products affected across 2 vendorsQuic GoQuic Go

Using quic-go by quic-go?

Get instant alerts when new vulnerabilities affect quic-go - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

quic-go is an implementation of the QUIC protocol in Go. Prior to version 0.59.1, an attacker can cause excessive memory allocation in quic-go's HTTP/3 client and server implementations by sending a QPACK-encoded HEADERS frame that decodes into a large trailer field section with many unique field names and/or large values. The implementation builds an `http.Header` for the corresponding `http.Request` or `http.Response`, while only enforcing limits on the size of the QPACK-compressed HEADERS frame, not on the decoded field section. This can lead to memory exhaustion. This is very similar to CVE-2025-64702. The difference is that this issue uses HTTP trailers, rather than HTTP headers, as the attack vector. A misbehaving or malicious peer can cause a denial-of-service (DoS) attack against quic-go's HTTP/3 servers or clients by triggering excessive memory allocation, potentially leading to crashes or resource exhaustion. This affects both servers and clients due to symmetric header construction. Version 0.59.1 enforces RFC 9114 decoded field section size limits for trailers as well. It incrementally decodes QPACK entries and checks the field section size after each entry, aborting the stream if an entry causes the limit to be exceeded.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.59.1
Affected range stops below 0.59.1, so it looks safe — our inference, not a vendor statement
v < 0.59.1
Affected range stops below 0.59.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_CONFIRMMitigationVendor Advisory
Source: cverecord
https://github.com/quic-go/quic-go/security/advisories/GHSA-vvgj-x9jq-8cj9
x_refsource_MISCProductRelease Notes
Source: cverecord
https://github.com/quic-go/quic-go/releases/tag/v0.59.1

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card