HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. Oct 8, 2026 · NIST NVD

   Detected

   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_TABL

2. Oct 15, 2026 · NIST NVD

   Updated

   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_TABL

Sources

• CVE.orgVulnerability recordCVE-2026-97032

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-97032

  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

  nvd.nist.gov

References

• Reference · go.dev
• Reference · go.dev
• Reference · go.dev
• Reference · groups.google.com
• Reference · groups.google.com
• Reference · pkg.go.dev