GHSA-9hxf-ppjv-w6rq is a medium-severity (CVSS 5.3) CWE-440 vulnerability in io.grpc:grpc-protobuf. A fix is available for io.grpc:grpc-protobuf — see the affected versions and patch details below.
gRPC connection termination issue
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-9hxf-ppjv-w6rq.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-9hxf-ppjv-w6rq plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.grpc:grpc-protobuf☕io.grpc:grpc-protobuf🐍grpcio🐍grpcio💎grpc💎grpcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven, PyPI packages — download data is not available via public APIs for these ecosystems.
Description
gRPC contains a vulnerability whereby a client can cause a termination of connection between a HTTP2 proxy and a gRPC server: a base64 encoding error for -bin suffixed headers will result in a disconnection by the gRPC server, but is typically allowed by HTTP2 proxies. We recommend upgrading beyond the commit in https://github.com/grpc/grpc/pull/32309.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.grpc:grpc-protobuf | ≥ 1.53.0&&< 1.53.1 | 1.53.1io.grpc:grpc-protobuf:1.53.1 |
| ☕Maven | io.grpc:grpc-protobuf | ≥ 1.54.0&&< 1.54.2 | 1.54.2io.grpc:grpc-protobuf:1.54.2 |
| 🐍PyPI | grpcio | ≥ 1.53.0&&< 1.53.1 | 1.53.1pip install --upgrade 'grpcio==1.53.1' |
| 🐍PyPI | grpcio | ≥ 1.54.0&&< 1.54.2 | 1.54.2pip install --upgrade 'grpcio==1.54.2' |
| 💎RubyGems | grpc | ≥ 1.53.0&&< 1.53.1 | 1.53.1bundle update grpc --conservative |
| 💎RubyGems | grpc | ≥ 1.54.0&&< 1.54.2 | 1.54.2bundle update grpc --conservative |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.grpc:grpc-protobuf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.grpc:grpc-protobuf to 1.53.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9hxf-ppjv-w6rq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9hxf-ppjv-w6rq can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9hxf-ppjv-w6rq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9hxf-ppjv-w6rq in your dependencies?
O3 Security finds GHSA-9hxf-ppjv-w6rq across Maven, PyPI, RubyGems dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.