CVE-2026-97054: Go standard library net/http · Missing Synchronization
Affects Go standard library net/httpSource CVE Database V5
Not known to be exploited : upgrade to 1.27.4 or 1.26.11 when convenient.
Data as of 11 Nov 2026, 03:33 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 1.27.4, 1.26.11
Exploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade Go standard library net/http to 1.27.4 or 1.26.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Go standard librarynet/http | Affected
| Fixed in
|
| Go standard librarynet/http | Affected
| Fixed in
|
Gonet/httppkg:golang/net/httpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.