CVE-2026-118488

Heap exhaustion via unbounded simple string or bulk string allocation in Vert.x Redis client

Published Nov 3, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-770
Type Values Removed Values Added
First Time appeared Eclipse
Eclipse vert.x
Eclipse Foundation
Eclipse Foundation vert.x
Weaknesses CWE-789
Vendors & Products Eclipse
Eclipse vert.x
Eclipse Foundation
Eclipse Foundation vert.x
Type Values Removed Values Added
Description 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.
Title Heap exhaustion via unbounded simple string or bulk string allocation in Vert.x Redis client
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Nov 3, 2026, 6:04 PM
Reserved
Oct 28, 2026, 11:32 AM
Status
Deferred
Published
Nov 3, 2026, 3:17 PM
Modified
Nov 3, 2026, 6:17 PM
Severity
Moderate
Public date
Nov 3, 2026, 3:13 PM