HTTP/1 server crash due to MaxBytesReader header race in net/http
Historical advisory saved 11 Nov 2026 04:27:36 UTC. The publisher may have updated it since then. Latest advisory.
osv · GO-2026-6859
PublishedFor 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.
- Source published
- 11 Nov 2026 02:51:11 UTC
- Source modified
- 11 Nov 2026 03:15:14 UTC
- Saved here
- 11 Nov 2026 04:27:36 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.