In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], a gRPC endpoint does have a configurable per message maximum size in bytes, however the maximum size applies to the received bytes. When applied to a compressed message, this only applies to the compressed size and not the actual size of the uncompressed content. This can be used to force a gRPC endpoint to allocate more bytes than the value defined by the configuration, making the endpoint vulnerable to compression bomb attacks. The impacted component is io.vertx:vertx-gprc-server.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 6
- Cpes+2 CPE criteria (now 2)NVD modified 2026-10-20 19:27
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-20 19:27
- CwesCWE-409NVD modified 2026-10-15 15:17
- StatusAwaiting Analysis → Undergoing AnalysisNVD modified 2026-10-15 15:17
- StatusReceived → Awaiting AnalysisNVD modified 2026-10-15 14:41
- First seenCVSS 8.7NVD modified 2026-10-15 09:17
Affected (CPE criteria) 2
cpe:2.3:a:eclipse:vert.x:*:*:*:*:*:*:*:*cpe:2.3:a:eclipse:vert.x:5.2.0:*:*:*:*:*:*:*
References 2
- https://github.com/eclipse-vertx/vertx-grpc/security/advisories/GHSA-4wvq-75mw-q6cg Vendor Advisory
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/349 Issue Tracking, Third Party Advisory