CVE-2026-97054

GO-2026-6859 · published 11 Nov 2026 · updated 17 Nov 2026

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

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 1.26.11, 1.27.4 and stdlib 1.27.4.

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 server that utilizes MaxBytesReader or MaxBytesHandler can crash due to runtime panic if its handler reads the request body concurrently with writing the response header.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
Go standard library<1.26.11, >=1.27.0-0 <1.27.41.26.11, 1.27.4
go: stdlib>=1.27.0-0 <1.27.41.27.4

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in stdlib (Go), strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97054 severity on Zeptric[![CVE-2026-97054](https://zeptric.io/badge/cve/CVE-2026-97054.svg)](https://zeptric.io/cve/CVE-2026-97054)