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.
Published:
2026-11-11
Score:
n/a
EPSS:
< 1% Very Low
KEV:
No
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
No advisories yet.
References
History
Wed, 11 Nov 2026 03:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | HTTP/1 server crash due to MaxBytesReader header race in net/http | |
| References |
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2026-11-11T03:13:17.877Z
Reserved: 2026-09-23T23:05:04.988Z
Link: CVE-2026-97054
No data.
Status : Received
Published: 2026-11-11T05:19:58.943
Modified: 2026-11-11T05:19:58.943
Link: CVE-2026-97054
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.