Impact
Envoy's ProdClusterManagerFactory::allocateConnPool incorrectly dereferences a null transport_socket_options pointer when selecting an HTTP/3 connection pool. Certain LoadBalancerContext implementations—used by synthetic, mirror, health‑check, and async‑client calls—can return no transport‑socket options, so routine traffic that hits those contexts with HTTP/3 enabled causes an Envoy worker to crash. The fault is a null pointer dereference (CWE‑476) and results in denial of service as the proxy process terminates.
Affected Systems
Envoy servers using any release of the 1.36, 1.37, 1.38, or 1.39 branches before the respective patch releases (1.36.10, 1.37.6, 1.38.4, and 1.39.1) are vulnerable when HTTP/3 is enabled and a context supplies no transport‑socket options. The vulnerability requires the HTTP/3 protocol set and context types such as synthetic, mirror, health‑check, or async‑client under auto_config.
Risk and Exploitability
The CVSS score of 5.9 indicates medium severity. EPSS is not available and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a remote client sending HTTP/3 requests that exercise the vulnerable code path. While the flaw does not provide direct code execution, the resulting crash can interrupt service availability and degrade system reliability.
OpenCVE Enrichment