HTTP/1 server crash due to MaxBytesReader header race in net/http

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2026-97054 · CVE overview and exploitation status

EUVD-2026-123113

GHSA-rg98-f588-44xg

GO-2026-6859

cve-program · CVE-2026-97054

• https://go.dev/cl/862185
• https://go.dev/issue/82563
• https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM
• https://pkg.go.dev/vuln/GO-2026-6859

euvd · EUVD-2026-123113

• https://go.dev/cl/862185
• https://go.dev/issue/82563
• https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM
• https://pkg.go.dev/vuln/GO-2026-6859

nvd · CVE-2026-97054

• https://go.dev/cl/862185
• https://go.dev/issue/82563
• https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM
• https://pkg.go.dev/vuln/GO-2026-6859

osv · GO-2026-6859

• https://go.dev/cl/862185
• https://go.dev/issue/82563
• https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM

• For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 se… · Advisory content revised · 15 Nov 2026
• For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another header being set explicitly in the server handler. As a result, an HTTP/1 se… · Advisory content revised · 13 Nov 2026
• HTTP/1 server crash due to MaxBytesReader header race in net/http · Newly collected advisory · 11 Nov 2026
• HTTP/1 server crash due to MaxBytesReader header race in net/http · Newly collected advisory · 11 Nov 2026