Go standard library · Go · published 2026-11-11
CVE-2026-97054HTTP/1 server crash due to MaxBytesReader header race in net/http
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-97054 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 32% of all CVEs. This Go vulnerability: CVSS 5.9 (v3.1). Fixed upstream in Go 1.27.4, 1.26.11; Ubuntu still has unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Go 1.27.4, 1.26.11.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | golang-1.24 | Won’t fix |
| 12 bookworm | golang-1.19 | Won’t fix | |
| Ubuntu (+28 more packages) | 26.04 LTS | golang-1.24 | No fix yet |
| 24.04 LTS | golang-1.24 | No fix yet | |
| 22.04 LTS | golang-1.24 | No fix yet |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Language runtimeGo
Go security releases: 1.27.4, 1.26.11
Upgrade to
1.27.41.26.11Why: Vendor security release for server software (most severe: CVE-2026-97040).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (33th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.9 (v3.1)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Go standard library net/http
0to before1.26.11(affected)1.27.0-0to before1.27.4(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.