Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97032 Overview
CVE-2026-97032 is a concurrency vulnerability affecting HTTP/2 server implementations in the Go golang.org/x/net/http2 package. The server modifies its HPACK encoder from two goroutines without synchronization. One goroutine encodes HEADERS frames when sending responses, while another modifies the encoder's table size when processing SETTINGS frames containing SETTINGS_HEADER_TABLE_SIZE values from clients. A malicious client can repeatedly send requests while changing the header table size to crash the server. The flaw is tracked as [CWE-362] race condition and listed as GO-2026-6617.
Critical Impact
Remote, unauthenticated attackers can crash HTTP/2 servers built on the affected Go networking package, producing a denial-of-service condition against public-facing services.
Affected Products
- Go golang.org/x/net/http2 package HTTP/2 server implementation
- Applications and services linking the vulnerable x/net/http2 module versions
- Downstream Go-based web servers, proxies, and API gateways using the affected package
Discovery Timeline
- 2026-10-08 - CVE-2026-97032 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-97032
Vulnerability Analysis
The vulnerability is a classic data race in the Go HTTP/2 server's HPACK encoder state. HPACK is the header compression format used by HTTP/2, defined in RFC 7541. The encoder maintains a dynamic table whose size can be renegotiated by the client via SETTINGS frames.
In the affected implementation, the response-writing goroutine calls into the HPACK encoder to serialize HEADERS frames. Simultaneously, the connection's frame-handling goroutine processes inbound SETTINGS frames and invokes SetMaxDynamicTableSize on the same encoder. These two paths touch shared encoder state without a mutex or channel-based serialization.
When both goroutines run concurrently, the encoder's internal data structures can become inconsistent. This triggers a runtime panic that terminates the server process, producing a denial-of-service outcome. Confidentiality and integrity are not affected.
Root Cause
The root cause is missing synchronization around the HPACK encoder instance shared between the writer loop and the settings handler. The encoder was treated as owned by a single goroutine, but the SETTINGS_HEADER_TABLE_SIZE handling path mutates it from a different goroutine. This violates Go's memory model and introduces an exploitable race.
Attack Vector
Exploitation requires only network access to the HTTP/2 endpoint and no authentication or user interaction. A malicious client opens an HTTP/2 connection, repeatedly issues requests that force the server to emit response headers, and interleaves SETTINGS frames that change SETTINGS_HEADER_TABLE_SIZE. The resulting race against the response-encoding path crashes the server. See Go Issue #81867 and the fixes in Go.dev CL #847188 and Go.dev CL #847313 for implementation detail.
Detection Methods for CVE-2026-97032
Indicators of Compromise
- Unexpected Go runtime panics referencing hpack, Encoder, writeFrame, or SetMaxDynamicTableSize in server logs
- Repeated process restarts or crash-loop behavior on HTTP/2 listeners under active client traffic
- HTTP/2 clients from a single source address sending unusually frequent SETTINGS frames with changing SETTINGS_HEADER_TABLE_SIZE values
Detection Strategies
- Inspect HTTP/2 frame telemetry for clients that send SETTINGS frames at high rates during active request streams
- Correlate server crash events with inbound HTTP/2 connections to identify malicious sources
- Use Go's -race build flag in staging environments to surface the data race in HPACK handling before deployment
Monitoring Recommendations
- Alert on abnormal process exit codes and panic signatures for Go HTTP/2 services
- Monitor request-rate anomalies on / and other HTTP/2 endpoints paired with elevated SETTINGS frame counts
- Capture packet traces at edge proxies to retain evidence of SETTINGS_HEADER_TABLE_SIZE manipulation
How to Mitigate CVE-2026-97032
Immediate Actions Required
- Update golang.org/x/net to the fixed version referenced in GO-2026-6617 and rebuild all Go binaries that embed the HTTP/2 server
- Inventory services exposing HTTP/2 and prioritize those reachable from untrusted networks
- Run govulncheck across your build pipeline to identify binaries still linking the vulnerable package
Patch Information
The Go project addressed the race in commits published as Go.dev CL #847188 and Go.dev CL #847313, announced on the golang-announce mailing list and a follow-up thread. Update to the fixed golang.org/x/net/http2 release and redeploy affected services.
Workarounds
- Terminate HTTP/2 at an upstream proxy (for example nginx or Envoy) that is not built on the vulnerable Go package, and forward HTTP/1.1 to the Go backend
- Disable HTTP/2 on the Go server by configuring the TLS listener to advertise only http/1.1 in ALPN until the patch can be deployed
- Rate-limit or drop clients that send excessive SETTINGS frames per connection at the network edge
# Update the vulnerable module and verify with govulncheck
go get golang.org/x/net@latest
go mod tidy
govulncheck ./...
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

