7.5
Élevée
CVE-2026-78659 When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the…
Description
When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
Produits et versions touchés
| Produit | Versions touchées | Corrigé en |
|---|---|---|
| net/http 1.26 | premières → < 1.26.9 | 1.26.9 |
| net/http/internal/http2 1.27 | 1.27.0-0 → < 1.27.2 | 1.27.2 |
| golang.org/x/net/http2 0.60 | premières → < 0.60.0 | 0.60.0 |
Autres CVE de net/http
Les 26 CVE de net/http →
CVE-2026-97032
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently
7.5
Élevée
CVE-2026-78667
When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS)…
7.5
Élevée
CVE-2026-94439
When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the…
7.5
Élevée
CVE-2026-78669
A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams…
7.5
Élevée