Live › vulnerability › CVE-2026-118488
Eclipse Vert.x's RESP and line-based parsers keep growing a buffer when a malicious server sends bytes without a line terminator, and a malformed RESP bulk string can make the parser loop on the same data. An attacker-controlled server can cause out-of-memory conditions in a client that reads from it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 15:21 UTC. All times on this page are UTC.
Applications built on Eclipse Vert.x 4.0.0 through 4.5.35 or 5.0.0 through 5.2.2 that connect to a server they do not fully trust, such as a Redis-protocol endpoint, and that buffer responses. Applications that only talk to trusted servers, or that do not use the affected parsers, are less exposed.
No product ranges from the sources yet.
mvn dependency:tree or gradle dependencies, and compare it to the affected ranges.4.5.35.5.2.2.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Eclipse Vert.x versions [4.0.0, 4.5.35] or [5.0.0, 5.2.2], when a malicious server keeps sending bytes on an EOL-terminated line (not length-prefixed, for example a simple string [1]), we'll keep growing the buffer without bounds, eventually leading to an OOM. We need to have a configurable limit for EOL-terminated lines.
If a malicious server sends a specially crafted RESP response (for example a bulk string [2] with missing CRLF trailer), the parser enters an infinite loop where it keeps parsing the same buffer and pushing the same response to the caller, which may lead e.g. to an OOM if the consumer just buffers the responses. We must fix the parser to avoid this infinite looping.
This page as .md · .json · in your agent: get_signal("CVE-2026-118488")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.