{"affected":[{"defaultStatus":"unaffected","ecosystem":"https://pkg.go.dev","packageName":"net/http","product":"net/http","source":"CNA: Go","vendor":"Go standard library","versions":[{"lessThan":"1.26.11","status":"affected","version":"0","versionType":"semver"},{"lessThan":"1.27.4","status":"affected","version":"1.27.0-0","versionType":"semver"}]}],"cveId":"CVE-2026-97054","cwes":["CWE-820"],"description":"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.","epss":null,"exploits":[],"kev":null,"metrics":[],"modifiedAt":1794366797877,"publishedAt":1794366797877,"references":[{"source":"CNA: Go","tags":[],"url":"https://go.dev/cl/862185"},{"source":"CNA: Go","tags":[],"url":"https://go.dev/issue/82563"},{"source":"CNA: Go","tags":[],"url":"https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM"},{"source":"CNA: Go","tags":[],"url":"https://pkg.go.dev/vuln/GO-2026-6859"}],"remediation":[],"revision":"609876a8a09a5b81b5d765c1c9e1b8edda2d2b331340d30af1195f8824714cde","sources":[{"modifiedAt":1794366797877,"name":"CNA: Go","retrievedAt":1794370203914,"url":"https://www.cve.org/CVERecord?id=CVE-2026-97054"}],"ssvc":null,"status":"published","title":"HTTP/1 server crash due to MaxBytesReader header race in net/http","updatedAt":1794370203914}