chore(deps): update module github.com/quic-go/quic-go to v0.59.1 [security]

[dwertent]

This PR contains the following updates:

Package	Type	Update	Change
github.com/quic-go/quic-go	indirect	patch	v0.59.0 → v0.59.1

---

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

CVE-2026-40898 / GHSA-vvgj-x9jq-8cj9

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.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.

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.Request or http.Response.

http3.Server.MaxHeaderBytes and http3.Transport.MaxResponseHeaderBytes limit 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 Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

• https://github.com/quic-go/quic-go/security/advisories/GHSA-vvgj-x9jq-8cj9
• https://nvd.nist.gov/vuln/detail/CVE-2026-40898
• https://github.com/quic-go/quic-go/pull/5642
• https://github.com/quic-go/quic-go/commit/c56e8c79d1627cc1ed6005b421b4b0adadd83665
• https://github.com/advisories/GHSA-g754-hx8w-x2g6
• https://github.com/quic-go/quic-go
• https://github.com/quic-go/quic-go/releases/tag/v0.59.1

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.1

Compare Source

This patch release backports #​5642, which adds validation for HTTP/3 trailers.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[dwertent]

ℹ️ Artifact update notice

File name: nodebuilder/tests/tastora/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.25.9 -> 1.25.11

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[dwertent]

Closing: opened during a CVE-remediation test session on 2026-06-15; not needed (superseded by consolidated grouped/direct-only/severity-filtered config). Sorry for the noise.