Loading
It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy and the backend such that other clients see failed requests. It's also possible to use this vulnerability to leak other clients HTTP header keys, but not values. This occurs because the error status for a misencoded header is not cleared between header reads, resulting in subsequent (incrementally indexed) added headers in the first request being poisoned until cleared from the HPACK table. Please update to a fixed version of gRPC as soon as possible. This bug has been fixed in 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4.
Cite this page
CVE-2024-7246. CVEDatabase.com. Retrieved 1 May 2026. https://cvedatabase.com/cve/CVE-2024-7246
Use CWE-440, Grpc vendor hub and Grpc product page to widen CVE-2024-7246 into its surrounding weakness, vendor, and product context.
Compare it with CVE-2023-44487, CVE-2017-9431 and CVE-2017-8359 for nearby disclosures in the same product family.