Vertx gRPC server does not limit the maximum message sizeGHSA-g76f-gjfx-4rpr
MEDIUMFix: eclipse-vertx/vertx-grpc@a76b14aGHSA-g76f-gjfx-4rpr is a medium-severity (CVSS 5.8) CWE-770 vulnerability in io.vertx:vertx-grpc-server. A fix is available for io.vertx:vertx-grpc-server — 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-g76f-gjfx-4rpr.
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
io.vertx:vertx-grpc-server☕io.vertx:vertx-grpc-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Eclipse Vert.x version 4.3.0 to 4.5.9, the gRPC server does not limit the maximum length of message payload (Maven GAV: io.vertx:vertx-grpc-server and io.vertx:vertx-grpc-client).
This is fixed in the 4.5.10 version.
Note this does not affect the Vert.x gRPC server based grpc-java and Netty libraries (Maven GAV: io.vertx:vertx-grpc)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.vertx:vertx-grpc-server | ≥ 4.3.0&&< 4.5.10 | 4.5.10io.vertx:vertx-grpc-server:4.5.10 |
| ☕Maven | io.vertx:vertx-grpc-client | ≥ 4.3.0&&< 4.5.10 | 4.5.10io.vertx:vertx-grpc-client:4.5.10 |
Affected Products
vert.xeclipseDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.vertx:vertx-grpc-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.vertx:vertx-grpc-server to 4.5.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g76f-gjfx-4rpr 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.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-g76f-gjfx-4rpr (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4 for Quarkus 3 | vertx-grpc-client | RHSA-2024:7052 |
| Red Hat build of Quarkus 3.8.6.redhat | io.vertx/vertx-grpc-client:4.5.7.redhat-00003 | RHSA-2024:6437 |
| Red Hat JBoss EAP XP 5.0 Update 1.0 | vertx-grpc | RHSA-2025:0542 |
| RHOSS-1.34-RHEL-8 | openshift-serverless-1/logic-data-index-ephemeral-rhel8:1.34.0-6 | RHSA-2024:8023 |
Frequently Asked Questions
Is GHSA-g76f-gjfx-4rpr in your dependencies?
Find it across Maven, including transitive dependencies.