Golang 1.10: For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically
Affects golang-1.10Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium.
Data as of 18 Nov 2026, 15:19 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 5.9 |
|---|
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10golang-1.26pkg:deb/ubuntu/golang-1.26?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10golang-1.27pkg:deb/ubuntu/golang-1.27?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.23pkg:deb/ubuntu/golang-1.23?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.24pkg:deb/ubuntu/golang-1.24?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.25pkg:deb/ubuntu/golang-1.25?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSgolang-1.26pkg:deb/ubuntu/golang-1.26?arch=source&distro=resoluteOther 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.
References
- ubuntu.com/security/CVE-2026-97054 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-97054 (opens in a new tab)
- groups.google.com/g/golang-announce/c/iY8TY0wWgbM/m/KsU1KfWgAQAJ (opens in a new tab)
- github.com/golang/go/issues/82563 (opens in a new tab)
- github.com/golang/go/commit/4c1752a033aef1a66eadfb11363ff256f8daf47d (opens in a new tab)
- github.com/golang/go/commit/0e6d155b1a4d2a994c7d906ce069949e17f4b8b8 (opens in a new tab)
- go.dev/cl/862185 (opens in a new tab)
- go.dev/issue/82563 (opens in a new tab)
- groups.google.com/g/golang-announce/c/iY8TY0wWgbM (opens in a new tab)
- pkg.go.dev/vuln/GO-2026-6859 (opens in a new tab)