Connected evidence
Follow a shared identifier, source page or planning group across source records. Dates show chronology; a connection does not establish cause, a shared rollout or applicability to your environment.
HTTP/1 server crash due to MaxBytesReader header race in net/http
Lead record- Why these records are connected
- Records explicitly naming the same CVE identifier.
- Connection key
cve:CVE-2026-97054- Public snapshot refreshed
- today 01:32 UTC
- Distinct source events
- 4
- Source records represented
- 4
Current snapshot membership is shown here. Source histories and cited revisions remain on each record. Future source targets are labelled separately from observed changes. Browse connections.
Evidence in chronological order
- Wed 11 Nov · Dated source evidence · Newly collected advisory HTTP/1 server crash due to MaxBytesReader header race in net/httpCVE-2026-97054 Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.Newly collected advisory; observed by ChangeIntel, not the original publication date.
- Wed 11 Nov · Dated source evidence · Newly collected advisory HTTP/1 server crash due to MaxBytesReader header race in net/httpGO-2026-6859 Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.Newly collected advisory; observed by ChangeIntel, not the original publication date.
- Fri 13 Nov · Dated source evidence · Advisory content revised 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 se…EUVD-2026-123113 Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.Advisory content revised; observed by ChangeIntel, not the original publication date.
- Sun 15 Nov · Dated source evidence · Advisory content revised 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 se…EUVD-2026-123113 Source: Derived from the linked evidence · source check: not recorded hereYour review: not selected in your watchlist or stack; no review is inferred.Advisory content revised; observed by ChangeIntel, not the original publication date.