Denial of Service Vulnerability in gRPC TCP Server (Posix-compatible platforms)GHSA-p25m-jpj4-qcrr
HIGHFix: grpc/grpc#33656GHSA-p25m-jpj4-qcrr is a high-severity (CVSS 7.5) CWE-248 vulnerability in grpcio. A fix is available for grpcio — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-p25m-jpj4-qcrr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
grpcio🐍grpcio🐍grpcio💎grpc💎grpc💎grpc💎grpcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Lack of error handling in the TCP server in Google's gRPC starting version 1.23 on posix-compatible platforms (ex. Linux) allows an attacker to cause a denial of service by initiating a significant number of connections with the server. Note that gRPC C++ Python, and Ruby are affected, but gRPC Java, and Go are NOT affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | grpcio | ≥ 1.55.0&&< 1.55.3 | 1.55.3pip install --upgrade 'grpcio==1.55.3' |
| 🐍PyPI | grpcio | ≥ 1.54.0&&< 1.54.3 | 1.54.3pip install --upgrade 'grpcio==1.54.3' |
| 🐍PyPI | grpcio | ≥ 1.53.0&&< 1.53.2 | 1.53.2pip install --upgrade 'grpcio==1.53.2' |
| 💎RubyGems | grpc | ≥ 1.56.0&&< 1.56.2 | 1.56.2bundle update grpc --conservative |
| 💎RubyGems | grpc | ≥ 1.55.0&&< 1.55.3 | 1.55.3bundle update grpc --conservative |
| 💎RubyGems | grpc | ≥ 1.54.0&&< 1.54.3 | 1.54.3bundle update grpc --conservative |
Affected Products
grpcgrpcDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for grpcio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update grpcio to 1.55.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p25m-jpj4-qcrr is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Satellite 6.14 for RHEL 8 | rubygem-grpc-0:1.58.0-1.el8sat | RHSA-2024:0797 |
Frequently Asked Questions
Is GHSA-p25m-jpj4-qcrr in your dependencies?
Find it across PyPI, RubyGems, including transitive dependencies.