chore(deps): update module github.com/quic-go/quic-go to v0.59.1 [security] (alauda-v0.65.0) - #182
Open
alaudaa-renovate[bot] wants to merge 1 commit into
Conversation
alaudaa-renovate
Bot
added
the
dependencies
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.57.1->v0.59.1HTTP/3 QPACK Trailer Expansion Memory Exhaustion in github.com/quic-go/quic-go
CVE-2026-40898 / GHSA-vvgj-x9jq-8cj9 / GO-2026-5676
More information
Details
HTTP/3 QPACK Trailer Expansion Memory Exhaustion in github.com/quic-go/quic-go
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
quic-go: HTTP/3 QPACK Trailer Expansion Memory Exhaustion
CVE-2026-40898 / GHSA-vvgj-x9jq-8cj9 / GO-2026-5676
More information
Details
Summary
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.Headerfor the correspondinghttp.Requestorhttp.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.
Impact
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.
Details
In HTTP/3, field sections are compressed using QPACK (RFC 9204). Field sections are used for both HTTP headers and trailers. quic-go's HTTP/3 server and client decode the QPACK-encoded HEADERS frame into header fields, then construct an
http.Requestorhttp.Response.http3.Server.MaxHeaderBytesandhttp3.Transport.MaxResponseHeaderByteslimit the encoded HEADERS frame size, with defaults of 1 MB for servers and 10 MB for clients. However, they did not limit the decoded field section size. A maliciously crafted HEADERS frame carrying trailers can expand to about 50x the encoded size using QPACK static table entries with long names and/or values.RFC 9114 requires endpoints to enforce decoded field section size limits via SETTINGS, which quic-go did not do for trailers.
The Fix
quic-go now 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.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
quic-go/quic-go (github.com/quic-go/quic-go)
v0.59.1Compare Source
This patch release backports https://github.com/quic-go/quic-go/pull/5642, which adds validation for HTTP/3 trailers.
v0.59.0Compare Source
This release adds a couple of new features:
ReceiveStreamandStream: #5501Breaking Changes
ClientHelloInfo: #5497ConnectionTracingIDandConnectionTracingKey: #5521ConnectionStatenow reports both the local and the remote status of the QUIC Datagram and Reliable Stream Reset extensions: #5533Other Notable Fixes
RecordEventandClose: #5523Changelog
Full Changelog: quic-go/quic-go@v0.58.0...v0.59.0
v0.58.1Compare Source
This patch release backports fixes for a bug in the PTO queueing logic that could lead to an infinite loop of PING packets.
Bug Fixes
v0.58.0Compare Source
This release optimizes the QUIC handshake:
Other notable changes
datagram_idonpacket_sent,packet_receivedandpacket_bufferedevents, using the CRC32 of the packet: #5455Changelog
Full Changelog: quic-go/quic-go@v0.57.0...v0.58.0
Configuration
📅 Schedule: Branch creation - "" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.