Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-7246: It's possible for a gRPC client communicating with a HTTP/2 proxy to poison the HPACK table between the proxy

32
This week
MEDIUM 5.3REMOTEUPGRADE

CVE-2024-7246 is a medium-severity flaw (CVSS 5.3) affecting grpc. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 requ

Why this priority

  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.2% (top 87%)
CISA exploited listNo
WeaknessCWE-440
Published2024-08-06
Last modified2026-06-17
Publisher (CNA): Google Inc. · Vendor: grpc

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

grpc grpc UPGRADE
Affected: < 1.58.3 · >= 1.59.0 and < 1.59.5 · >= 1.60.0 and < 1.60.2 · >= 1.61.0 and < 1.61.3 · >= 1.62.0 and < 1.62.3 · >= 1.63.0 and < 1.63.2 · >= 1.64.0 and < 1.64.3 · >= 1.65.0 and < 1.65.4
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
Safe to downgrade to: a release before 1.59.0
1. Check installed version
apt-cache policy grpc || rpm -q grpc || grpc --version
2. UPGRADE to 1.58.3 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade grpc
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade grpc
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 1.59.0 (Debian / Ubuntu)
apt-cache madison grpc sudo apt install grpc=<VERSION_BEFORE_1.59.0> sudo apt-mark hold grpc
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list grpc sudo dnf downgrade grpc-<VERSION_BEFORE_1.59.0> sudo dnf versionlock add grpc
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-7246?

grpc: upgrade to 1.58.3, 1.59.5, 1.60.2, 1.61.3, 1.62.3, 1.63.2, 1.64.3, 1.65.4. Exact commands for each OS are on this page.

Is CVE-2024-7246 being exploited?

CVE-2024-7246 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-7246 affect?

CVE-2024-7246 affects grpc. Severity is medium (CVSS 5.3). 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 HT

How urgent is CVE-2024-7246?

Priority 32/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.