# CVE-2025-64702: GO-2025-4233 - HTTP/3 QPACK Header Expansion DoS in github.com/quic-go/quic-go

Source: https://junglewise.ai/threats/cve-2025-64702-quic-go-http-3-qpack-header-expansion-dos  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-12-11  
License: CC BY 4.0 with a link back

CVE-2025-64702 · Severity: medium · CVSS 5.3 · Published 2025-12-11

quic-go is an implementation of the QUIC protocol in Go. Versions 0.56.0 and below are vulnerable to excessive memory allocation through quic-go's HTTP/3 client and server implementations by sending a QPACK-encoded HEADERS frame that decodes into a large header field section (many unique header names and/or large values). The implementation builds an http.Header (used on the http.Request and http.Response, respectively), while only enforcing limits on the size of the (QPACK-compressed) HEADERS frame, but not on the decoded header, leading to memory exhaustion. This issue is fixed in version 0.57.0.

Technologies: [github.com/quic-go/quic-go (Go)](https://junglewise.ai/threats/technologies/github-com-quic-go-quic-go). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-64702 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-64702 being exploited in the wild.

**How severe is CVE-2025-64702?** Medium severity, with a CVSS score of 5.3, published 11 December 2025.

**Which products and versions are affected?** github.com/quic-go/quic-go (Go) SEMVER:introduced=0,fixed=0.57.0.

**Is there a fix for CVE-2025-64702?** Yes. github.com/quic-go/quic-go (Go): upgrade to 0.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-64702?** Check whether you run github.com/quic-go/quic-go (Go) or Quic-Go Project 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.57.0 or later

  ```sh
  go get github.com/quic-go/quic-go@v0.57.0
  ```


## Affected products

- github.com/quic-go/quic-go (Go) SEMVER:introduced=0,fixed=0.57.0
- Quic-Go Project Quic-Go

## Identifiers

- CVE-2025-64702
- GHSA-g754-hx8w-x2g6
- GO-2025-4233

## Related threats

- [quic-go memory exhaustion in HTTP/3 trailers](https://junglewise.ai/threats/cve-2026-40898-quic-go-memory-exhaustion-in-http-3-trailers)
- [GO-2025-4017 - Panic occurs when queuing undecryptable packets after handshake completion in github.com/quic-go/quic-go](https://junglewise.ai/threats/cve-2025-59530-quic-go-panic-occurs-when-queuing-undecryptable-packets-after)
- [GO-2025-3735 - Panic in Path Probe Loss Recovery Handling in github.com/quic-go/quic-go](https://junglewise.ai/threats/cve-2025-29785-quic-go-has-panic-in-path-probe-loss-recovery-handling)
- [GO-2024-3302 - ICMP Packet Too Large Injection Attack on Linux in github.com/quic-go/quic-go](https://junglewise.ai/threats/cve-2024-53259-quic-go-affected-by-an-icmp-packet-too-large-injection-attack-on)
- [GO-2024-2682 - Denial of service via connection starvation in github.com/quic-go/quic-go](https://junglewise.ai/threats/cve-2024-22189-quic-s-connection-id-mechanism-vulnerable-to-memory-exhaustion)