HTTP/1 server connection desynchronization after 2xx CONNECT response in net/http

These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.

CVE-2026-94439 · Microsoft / collected KEV context

EUVD-2026-95428

GHSA-2gfw-j3c5-j46w

GO-2026-6613

BIT-golang-2026-94439

cve-program · CVE-2026-94439

• https://go.dev/cl/847311
• https://go.dev/issue/81744
• https://groups.google.com/g/golang-announce/c/U2fTuyDJznI
• https://pkg.go.dev/vuln/GO-2026-6613

euvd · EUVD-2026-95428

• https://go.dev/cl/847311
• https://go.dev/issue/81744
• https://groups.google.com/g/golang-announce/c/U2fTuyDJznI
• https://pkg.go.dev/vuln/GO-2026-6613

nvd · CVE-2026-94439

• https://go.dev/cl/847311
• https://go.dev/issue/81744
• https://groups.google.com/g/golang-announce/c/U2fTuyDJznI
• https://pkg.go.dev/vuln/GO-2026-6613

osv · GO-2026-6613

• https://go.dev/cl/847311
• https://go.dev/issue/81744
• https://groups.google.com/g/golang-announce/c/U2fTuyDJznI

• When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CO… · Advisory content revised · 1 Nov 2026