Skip to main content
CVE-2026-97054VulnerabilityPublished

For HTTP/1 servers, when MaxBytesReader's limit is exceeded, "Connection: close" header is automatically set without

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-97054· High

Not known to be exploited : upgrade to 1.27.4 or 1.26.11 soon.

Data as of 11 Nov 2026, 07:48 UTC

Severity
High

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

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Go standard librarynet/httpAffected
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.27.4
Go standard librarynet/httpAffected
  • <1.26.11
Fixed in
  • 1.26.11
Gonet/httppkg:golang/net/httpOther threatsAffected
  • <1.26.11
  • >=1.27.0-0 <1.27.4
Fixed in
  • 1.26.11
  • 1.27.4

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.

References

Community reviews

Loading reviews…