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
Configurations
No configuration.
History
15 Oct 2026, 16:18
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-362 | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 7.5 |
08 Oct 2026, 23:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-08 23:17
Updated : 2026-10-15 16:18
NVD link : CVE-2026-97032
Mitre link : CVE-2026-97032
CVE.ORG link : CVE-2026-97032
JSON object : View
Products Affected
No product.
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
