CVE-2025-64702
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-11

Last updated on: 2026-02-17

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-11
Last Modified
2026-02-17
Generated
2026-05-07
AI Q&A
2025-12-11
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
quic-go_project quic-go to 0.57.0 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-770 The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in quic-go (versions 0.56.0 and below) involves excessive memory allocation caused by the HTTP/3 client and server implementations processing a QPACK-encoded HEADERS frame. The frame can decode into a large header field section with many unique header names or large values. While the implementation limits the size of the compressed HEADERS frame, it does not limit the size of the decoded headers, which can lead to memory exhaustion.


How can this vulnerability impact me? :

The vulnerability can lead to memory exhaustion on systems running vulnerable versions of quic-go. This could cause denial of service or degraded performance due to excessive memory consumption when processing specially crafted HTTP/3 HEADERS frames.


What immediate steps should I take to mitigate this vulnerability?

Upgrade quic-go to version 0.57.0 or later, as this version contains the fix for the excessive memory allocation vulnerability caused by processing large QPACK-encoded HEADERS frames.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart