Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 14 Nov 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-632 |
Sat, 14 Nov 2026 05:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Go Standard Library
Go Standard Library net/http |
|
| Vendors & Products |
Go Standard Library
Go Standard Library net/http |
Sat, 14 Nov 2026 04:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-632 |
Thu, 12 Nov 2026 06:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-632 |
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 |
|
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 : Awaiting Analysis
Published: 2026-11-11T05:19:58.943
Modified: 2026-11-12T22:09:39.233
Link: CVE-2026-97054
No data.
OpenCVE Enrichment
Updated: 2026-11-14T22:30:02Z