Skip to main content
VulnerabilityPublished Updated

CVE-2026-97032: Go standard library net/http · Race Condition

Affects Go standard library net/httpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.26.9 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.26.9, 1.27.2, 0.60.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 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 17 Nov 2026.

What to do

Upgrade net/http to 1.26.9; net/http/internal/http2 to 1.27.2; golang.org/x/net/http2 to 0.60.0.

Affected software

ProductAffectedFixed in
Go standard librarynet/httpAffected
  • <1.26.9
Fixed in
  • 1.26.9
Go standard librarynet/http/internal/http2Affected
  • >=1.27.0-0 <1.27.2
Fixed in
  • 1.27.2
golang.org/x/netgolang.org/x/net/http2Affected
  • <0.60.0
Fixed in
  • 0.60.0
Gonet/httppkg:golang/net/httpOther threatsAffected
  • <1.26.9
Fixed in
  • 1.26.9
Gonet/http/internal/http2pkg:golang/net/http/internal/http2Other threatsAffected
  • >=1.27.0-0 <1.27.2
Fixed in
  • 1.27.2
Gogolang.org/x/net/http2pkg:golang/golang.org/x/net/http2Other threatsAffected
  • <0.60.0
Fixed in
  • 0.60.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider mitigating by limiting or filtering suspicious HTTP/2 SETTINGS frames from clients or applying network-level protections to reduce exposure to malicious clients. Monitor vendor advisories for official patches or updates.

Description

HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

References

Community reviews

Loading reviews…