Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Google

  2. · 8 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-7246, by who scored it
Scored byCVSSScoreVector
GoogleCNA (assigner)4.0Medium6.3CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L
NVDNVD · Analyzed4.0Medium6.3CVSS: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
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.3.

Affected products

  • Google · gRPC

    • affected 1.53.0
    • affected 1.53.1
    • affected 1.53.2
    • affected 1.54.0
    • affected 1.54.1
    • affected 1.54.3
    • affected 1.55.0
    • affected 1.55.1
    • affected 1.55.3
    • affected 1.55.4
    • affected 1.56.0
    • affected 1.56.1
    • affected 1.56.2
    • affected 1.56.3
    • affected 1.56.4
    • affected 1.57.0
    • affected 1.57.1
    • affected 1.58.0
    • affected 1.58.1
    • affected 1.58.2
    • affected 1.59.0
    • affected 1.59.1
    • affected 1.59.2
    • affected 1.59.3
    • affected 1.59.4
    • affected 1.60.0
    • affected 1.60.1
    • affected 1.61.0
    • affected 1.61.1
    • affected 1.62.0
    • affected 1.61.2
    • affected 1.62.1
    • affected 1.62.2
    • affected 1.63.0
    • affected 1.63.1
    • affected 1.64.0
    • affected 1.64.1
    • affected 1.64.2
    • affected 1.65.0
    • affected 1.65.1
    • and 2 more

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-7246 badge
[![CVE-2024-7246](https://cveledger.app/badge/CVE-2024-7246.svg)](https://cveledger.app/cve/CVE-2024-7246)

Record last updated .