7.5
Élevée
CVE-2026-78660 Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they…
Description
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.
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 |
Références
- go.dev go.dev
- go.dev go.dev
- go.dev go.dev
- groups.google.com groups.google.com
- pkg.go.dev pkg.go.dev
Chronologie
- Publiée
- Dernière modification
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-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
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-78663
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream…
9.1
Critique