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], the Vert.x Redis client RESP parser pre-allocates arrays to a length declared by the server without enforcing an upper bound. A malicious or compromised Redis server, or an attacker in a man-in-the-middle position, can send a crafted RESP response declaring an extremely large array, push, or attribute length, causing the client to attempt a massive heap allocation. The resulting OutOfMemoryError crashes the Vert.x event loop thread, denying service to all connections and verticles sharing that loop. The impacted component is io.vertx:vertx-mysql-client.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/vert-x3/vertx-redis-client/security/advisories/GHSA-4wf9-p5hg-98w5 Vendor Advisory
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:31
- StatusUndergoing Analysis → AnalyzedNVD modified 2026-10-20 19:31
- CwesCWE-770NVD 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.2NVD modified 2026-10-15 08:16
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/vert-x3/vertx-redis-client/security/advisories/GHSA-4wf9-p5hg-98w5 Vendor Advisory
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/343 Issue Tracking, Third Party Advisory