For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without
Source GCVE Database
Not known to be exploited : upgrade to 1.27.4 or 1.26.11 soon.
Data as of 11 Nov 2026, 07:48 UTC
Rated High by Threat Radar's AI analysis · 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 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
A race condition in HTTP/1 servers using MaxBytesReader or MaxBytesHandler can cause a runtime panic and crash when the request body reading and response header writing occur concurrently after exceeding the MaxBytesReader limit.