t'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.
| Link | Resource |
|---|---|
| https://github.com/grpc/grpc/issues/36245 | Exploit Issue Tracking Patch |
Configuration 1 (hide)
|
22 Jul 2025, 19:29
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | NVD-CWE-noinfo | |
| References | () https://github.com/grpc/grpc/issues/36245 - Exploit, Issue Tracking, Patch | |
| CPE | cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:* | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.3 |
| First Time |
Grpc
Grpc grpc |
06 Aug 2024, 16:30
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Published : 2024-08-06 11:16
Updated : 2025-07-22 19:29
NVD link : CVE-2024-7246
Mitre link : CVE-2024-7246
CVE.ORG link : CVE-2024-7246
JSON object : View