CVE-2024-7246: grpc — Exploit & Fix

Description

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.

Is your site exposed to CVE-2024-7246?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

5.3

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Weakness Type (CWE)

CWE-440 CWE-440

Affected Products

Vendor	Product	Versions
grpc	grpc	< 1.58.3
grpc	grpc	1.59.0 — 1.59.5
grpc	grpc	1.60.0 — 1.60.2
grpc	grpc	1.61.0 — 1.61.3
grpc	grpc	1.62.0 — 1.62.3
grpc	grpc	1.63.0 — 1.63.2
grpc	grpc	1.64.0 — 1.64.3
grpc	grpc	1.65.0 — 1.65.4

References

Advisories & Patches

https://github.com/grpc/grpc/issues/36245

Exploits

https://github.com/grpc/grpc/issues/36245

Frequently Asked Questions

What is CVE-2024-7246? +

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. It has a CVSS v3.1 base score of 5.3 (MEDIUM).

How severe is CVE-2024-7246? +

CVE-2024-7246 has a CVSS v3.1 score of 5.3 out of 10, rated MEDIUM. This is a medium-severity vulnerability that should be remediated as part of regular maintenance.

What products are affected by CVE-2024-7246? +

CVE-2024-7246 affects products from grpc, specifically: grpc. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2024-7246? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-16769

An unencrypted 'pause encryption request' message causes a denial of service in the in the RS9116W/SiWx917. See vulnerability B-E10 in …

CVE-2026-97687

urllib3 is an HTTP client library for Python. From 1.26.0 until 2.8.0, the proxy_ssl_context, proxy_assert_hostname, proxy_assert_fingerprint, ssl_context, cert_reqs, verify_mode, use_forwarding_for_https=True, …

CVE-2024-32971 9.0

Apollo Router is a configurable, graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. …

CVE-2025-8850 8.8

In danny-avila/librechat version 0.7.9, there is an insecure API design issue in the 2-Factor Authentication (2FA) flow. The system allows …

CVE-2024-30246 7.6

Tuleap is an Open Source Suite to improve management of software developments and collaboration. A malicious user could exploit this …

CVE-2025-52953 6.5

An Expected Behavior Violation vulnerability in the routing protocol daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved …

CVE-2024-7246