Go HTTP/1 server crash from MaxBytesReader header race (CVE-2026-97054)
Identifiers: CVE-2026-97054 · GO-2026-6859
- Published
- Last substantive change
- Last verified
Last verified: . Attention items are due for re-verification within 72 hours.
Summary
Go 1.26.11 and 1.27.4, released 11 November 2026, fix a race in the standard net/http server. When a request body exceeds a MaxBytesReader or MaxBytesHandler limit, the server sets a Connection close header without synchronization. If the handler is reading the body while concurrently writing response headers, the program can panic and the whole process exits. Tracked as GO-2026-6859.
Impact
Denial of service of a Go HTTP/1 service through a crash; one oversized request at the wrong moment can stop the process until it restarts. No data disclosure or code execution is described. Services that never use MaxBytesReader or MaxBytesHandler, or never write headers while still reading the body, are outside the described path, though they should still be rebuilt on the next cycle.
Who is affected
Affected: Go 1.26 before 1.26.11 and Go 1.27 before 1.27.4. The OSV range starts at version 0, so older unsupported branches are also in scope and have no current upstream fix. Only HTTP/1 serving is described, and only when a handler limits the body with MaxBytesReader or MaxBytesHandler, the body exceeds that limit, and the handler reads the body concurrently with writing response headers. The fix is in the standard library, which is compiled into each binary; a service stays affected until it is rebuilt with a patched toolchain and the new binary is deployed and restarted. Updating Go on the host alone does not patch an existing binary. A vendor-maintained toolchain that documents a backport of this fix may also count, with that vendor evidence; a version string on its own, without vendor documentation or the rebuild and redeploy evidence, does not. The eleven other fixes in the same release are build-time issues in the Go toolchain, compiler and linker, triggered by building malicious packages or build inputs. Not all require cgo: some involve directives in non-cgo Go source files or .syso object files in pure-Go packages. They affect build machines that compile untrusted code, not a running service, and are not remote code execution in a deployed binary.
Products and versions
| Products and versions | Affected | Fixed |
|---|---|---|
| Go standard library net/http | <1.26.11; >=1.27.0-0, <1.27.4 | 1.26.11; 1.27.4, or documented vendor backport in the deployed build |
Exploitation evidence
Exploitation not established. No active exploitation was established in the reviewed sources, and the CVE was not in CISA KEV at review time. Absence is not proof.
Actions
- Ask whoever builds each Go service which toolchain produced the binary currently serving traffic; Go embeds that version in the binary.
- Rebuild with Go 1.26.11 or 1.27.4, deploy, restart, and record the new build ID or image digest.
- Keep the previous artifact and deployment definition so a rollback is a redeploy, not a rebuild.
- Acceptance, in authorized staging or your normal regression run: the process starts cleanly, an over-limit upload sent through the ordinary business flow is refused with the expected response while the process stays up, and error rates stay flat afterwards. That is bounded evidence the deployment works, not proof the race can never fire.
- If your CI builds third-party Go code, apply the same toolchain update there for the build-time fixes.
Unknowns
- Whether a given service uses MaxBytesReader or MaxBytesHandler and reads bodies concurrently with header writes; that lives in application code.
- How often the race fires in practice; upstream describes it as possible, not guaranteed per request.
- Which vendor appliances or SaaS tools embed Go in a way you cannot rebuild; those depend on vendor releases.
Sources
- Go vulnerability database https://vuln.go.dev/ID/GO-2026-6859.json
- Go security team https://groups.google.com/g/golang-announce/c/iY8TY0wWgbM
- CISA https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
Change history
- — Published: Published 12 November 2026 from the Go security release of 11 November 2026 and OSV record GO-2026-6859.