Skip to main content
MEDIUM

CVE-2024-7246

CVSS v3

5.3

MEDIUM

EPSS Score

0.2 %

exploit probability, as of 2026-10-19

CISA KEV

No

known exploited

Exploitation

—

SSVC status

Get an alert for each new CVE published for grpc.

Set up CVE WatchFree account · no credit card

Affected and fixed versions

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2024-7246 Red Hat Product Security38 products fixed · 1 known affected

    grpc: client communicating with a HTTP/2 proxy can poison the HPACK table between the proxy and the backend

    3scale-amp-apicast-gateway-container as a component of Red Hat 3scale API Management Platform 2

  • RHSA-2025:1335 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: RHUI 4.11 security, bugfix, and enhancement update

  • RHSA-2024:8906 Red Hat Product Security8 products fixed

    Red Hat Security Advisory: Satellite 6.16.0 release

  • RHSA-2024:6428 Red Hat Product Security26 products fixed

    Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.4 Product Security and Bug Fix Update

Full record on NVD

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.

Technical details

Published
2024-08-06

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.

Is CVE-2024-7246 actively exploited?

Active exploitation of CVE-2024-7246 has not been confirmed. Its EPSS score was 0.2% on 2026-10-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-7246?

CVE-2024-7246 has a CVSS v3 base score of 5.3 (MEDIUM severity).

Running grpc? Hear about its next vulnerability

CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.

Get alerts for this productCISA KEV additions, October 2026Search CVEs

Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database