For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set…
Historical advisory recorded 17 Nov 2026 08:28:59 UTC. Read the latest advisory.
nvd · CVE-2026-97054
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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
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
nvd · CVE-2026-97054
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.