CVE-2024-7246 | HPACK table poisoning in gRPC C++, Python & Ruby

Exp

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.

Published: 2024-08-06 Last update: 2025-07-22 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-7246 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-7246

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-7246

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.05% 0.04% -0.02%
2 2025-11-18 0.03% 0.05% +0.02%
3 2025-07-23 — 0.03% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-7246

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 4.0 MEDIUM
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network.
Attack complexity (AC:H)
Exploitation depends on constrained or hard-to-reproduce conditions.
Attack requirements (AT:N)
No additional preconditions are required beyond normal reachability.
Privileges required (PR:N)
No privileges are required.
User interaction (UI:N)
No user interaction is required.
Vulnerable system confidentiality impact (VC:N)
No confidentiality impact on the vulnerable system.
Vulnerable system integrity impact (VI:N)
No integrity impact on the vulnerable system.
Vulnerable system availability impact (VA:L)
Limited availability impact on the vulnerable system.
Subsequent system confidentiality impact (SC:N)
No confidentiality impact on subsequent systems.
Subsequent system integrity impact (SI:N)
No integrity impact on subsequent systems.
Subsequent system availability impact (SA:L)
Limited availability impact on subsequent systems.
Exploit maturity (threat) (E:X)
Not defined: no reliable threat intelligence; scoring assumes the worst case (equivalent to Attacked).
Confidentiality requirement (CR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Integrity requirement (IR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Availability requirement (AR:X)
Not defined: insufficient information; scoring treats this like High (worst case).
Modified attack vector (MAV:X)
Not defined: scoring uses the Base Attack Vector (AV).
Modified attack complexity (MAC:X)
Not defined: scoring uses the Base Attack Complexity (AC).
Modified attack requirements (MAT:X)
Not defined: scoring uses the Base Attack Requirements (AT).
Modified privileges required (MPR:X)
Not defined: scoring uses the Base Privileges Required (PR).
Modified user interaction (MUI:X)
Not defined: scoring uses the Base User Interaction (UI).
Modified vulnerable system confidentiality impact (MVC:X)
Not defined: scoring uses the Base VC metric.
Modified vulnerable system integrity impact (MVI:X)
Not defined: scoring uses the Base VI metric.
Modified vulnerable system availability impact (MVA:X)
Not defined: scoring uses the Base VA metric.
Modified subsequent system confidentiality impact (MSC:X)
Not defined: scoring uses the Base SC metric.
Modified subsequent system integrity impact (MSI:X)
Not defined: scoring uses the Base SI metric.
Modified subsequent system availability impact (MSA:X)
Not defined: scoring uses the Base SA metric.
Safety (supplemental) (S:X)
Not evaluated.
Automatable (supplemental) (AU:X)
Not evaluated.
Recovery (supplemental) (R:X)
Not evaluated.
Value density (supplemental) (V:X)
Not evaluated.
Vulnerability response effort (supplemental) (RE:X)
Not evaluated.
Provider urgency (supplemental) (U:X)
Not evaluated.
 — — [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2024-7246

OS Trackers for CVE-2024-7246

vendor priority summary link
alpine — CVE-2024-7246: 1 source package rows (grpc); 5 state rows across 3 repos (3.20-community, 3.22-community, edge-community); fixed 0, open 5. https://security.alpinelinux.org/vuln/CVE-2024-7246
debian not yet assigned CVE-2024-7246 not yet assigned priority: Debian including 1 source packages (grpc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2024-7246
redhat medium — https://access.redhat.com/security/cve/CVE-2024-7246
suse medium CVE-2024-7246 severity moderate: SUSE including 283 source package names (0.3.2-1.2:libgrpc++1_60-1.60.0-150600.15.3.1, 0.3.2-1.2:libgrpc37-1.60.0-150600.15.3.1, …), 414 product×package rows across 78 product lines (Container containers/lmcache-vllm-openai, Container containers/milvus, … (78 product lines)): Known Affected 231, Fixed 119, Known Not Affected 64. https://www.suse.com/security/cve/CVE-2024-7246/
ubuntu medium CVE-2024-7246 medium priority: Ubuntu including 1 source packages (grpc), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): needs-triage 7, ignored 2. https://ubuntu.com/security/CVE-2024-7246

Affected software / configurations for CVE-2024-7246

Vendor Product Version Raw CPE
grpc grpc < 1.58.3 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.59.0, < 1.59.5 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.60.0, < 1.60.2 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.61.0, < 1.61.3 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.62.0, < 1.62.3 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.63.0, < 1.63.2 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.64.0, < 1.64.3 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*
grpc grpc >= 1.65.0, < 1.65.4 cpe:2.3:a:grpc:grpc:*:*:*:*:*:-:*:*

References for CVE-2024-7246

URL Tags
https://github.com/grpc/grpc/issues/36245 Exploit Issue Tracking Patch
cvelogic Threat Intelligence