BIT-golang-2026-78660Published
HTTP/2 transport accepts malformed framing-related headers in net/http
Explicit identifiers and source references
These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.
CVE-2026-78660 · Microsoft / collected KEV context
cve-program · CVE-2026-78660
- https://go.dev/cl/835145
- https://go.dev/cl/836385
- https://go.dev/issue/81115
- https://groups.google.com/g/golang-announce/c/U2fTuyDJznI
- https://pkg.go.dev/vuln/GO-2026-6610
euvd · EUVD-2026-95425
- https://go.dev/cl/835145
- https://go.dev/cl/836385
- https://go.dev/issue/81115
- https://groups.google.com/g/golang-announce/c/U2fTuyDJznI
- https://pkg.go.dev/vuln/GO-2026-6610
nvd · CVE-2026-78660
- https://go.dev/cl/835145
- https://go.dev/cl/836385
- https://go.dev/issue/81115
- https://groups.google.com/g/golang-announce/c/U2fTuyDJznI
- https://pkg.go.dev/vuln/GO-2026-6610
osv · GO-2026-6610
Related operational evidence
Explicit CVE identifiers- 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 con… · Advisory content revised · 5 Nov 2026
- 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 con… · Advisory content revised · 1 Nov 2026
- 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 con… · Advisory content revised · 30 Oct 2026