
早上一醒看到 CI 挂了,就发现原来是又有 Go 的漏洞披露了 CVE-2026-97054 ,赶快去升级了下
Post summary
The post discloses CVE-2026-97054 affecting Go and indicates the author applied an upgrade in response, but offers no PoC, exploit details, or evidence of active exploitation.
Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
STABLE
| Date | Total | Labels |
|---|
| 2026-11-11 | 2 | Disclosure1Patch1 |
| 2026-11-12 | 1 | Patch1 |

早上一醒看到 CI 挂了,就发现原来是又有 Go 的漏洞披露了 CVE-2026-97054 ,赶快去升级了下
Post summary
The post discloses CVE-2026-97054 affecting Go and indicates the author applied an upgrade in response, but offers no PoC, exploit details, or evidence of active exploitation.

This security patch might not apply to you. OPA 1.22.4 fixes CVE-2026-97054, a crash in Go's HTTP/1 server. The fix comes from the Go version OPA is built with. Official binaries or Docker images: upgrade. Building OPA yourself: update your Go toolchain. https://t.co/0TMOLtv2jU

The networking one is CVE-2026-97054: an HTTP/1 server using MaxBytesReader can hit "concurrent map writes" when a body goes over the limit while another goroutine sets headers. That's a fatal error, not a recoverable panic: the whole process dies. Only a rebuilt binary fixes it.
Post summary
The text discloses CVE-2026-97054 with technical details about a concurrent map writes issue in an HTTP/1 server using MaxBytesReader, and notes that only a rebuilt binary fixes it.

CVE-2026-97054 For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without synchronization, which might race with another he… https://www.cve.org/CVERecord?id=CVE-2026-97054
Post summary
The text discloses CVE-2026-97054 by describing a race condition in HTTP/1 servers involving MaxBytesReader and the Connection: close header. No exploit code, patch, or active exploitation is mentioned.