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.
Metrics
CVSS 3.1 7.5/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NWeakness enumeration
Affected software
Source: the vendor's advisory (CNA). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Go standard library | net/http | < 1.26.9 |
| Go standard library | net/http/internal/http2 | >= 1.27.0-0, < 1.27.2 |
| golang.org/x/net | golang.org/x/net/http2 | < 0.60.0 |
References
Timeline
- Published
- Oct 8, 2026
- Last modified
- Oct 9, 2026
- NVD status
- Awaiting Analysis