No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Mon, 16 Nov 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-632 |
Mon, 16 Nov 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 16 Nov 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-362 CWE-820 |
|
| Metrics |
cvssV3_1
|
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 |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Go
Published:
Updated: 2026-11-16T16:01:26.695Z
Reserved: 2026-09-23T23:05:04.988Z
Link: CVE-2026-97054
Updated: 2026-11-16T16:01:18.304Z
Status : Awaiting Analysis
Published: 2026-11-11T05:19:58.943
Modified: 2026-11-16T16:17:56.290
Link: CVE-2026-97054
No data.
OpenCVE Enrichment
Updated: 2026-11-16T20:30:22Z