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.
Published: 2026-11-03
Score: 5.9 Medium
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Apply Patch
AI Analysis

Impact

In Eclipse Vert.x Redis client versions between 4.0.0 and 4.5.35, and between 5.0.0 and 5.2.2, the client will accept EOL‑terminated simple strings or bulk strings from a server without enforcing a maximum length. The parser will keep enlarging its internal buffer until memory exhaustion occurs, resulting in an out‑of‑memory condition. A second flaw allows a specially crafted RESP bulk string that lacks the required CRLF trailer to cause the parser to loop indefinitely on the same data, potentially feeding a consumer with repeated responses and leading to further memory consumption or an OOM. The primary impact is a denial of service by exhausting application memory resources.

Affected Systems

The vulnerability affects the Eclipse Vert.x framework, specifically the Vert.x Redis client component. Affected releases include Vert.x 4.0.0 through 4.5.35 and Vert.x 5.0.0 through 5.2.2. Applications that use any of these versions to communicate with a Redis server are at risk if the server sends oversized or malformed responses.

Risk and Exploitability

The CVSS score of 5.9 places the vulnerability in a moderate severity range. EPSS data is not available, and the issue is not listed in the CISA KEV catalog. A remote attacker who can control or manipulate the Redis server can send malicious RESP data to any application utilizing a vulnerable Vert.x client. Crafting an unlimited sequence of simple strings or a malformed bulk string would cause the client to continually consume memory or spin in an endless parse loop, leading to an application crash or a denial of service.

Generated by OpenCVE AI on November 3, 2026 at 16:49 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Eclipse Vert.x to a release that contains the parser limits and infinite‑loop fixes (for example, version 4.5.36 or later, or 5.2.3 or later).
  • Configure the Vert.x Redis client to set a maximum size for EOL‑terminated lines so that the internal buffer cannot grow without bound.
  • Validate that all RESP bulk strings received from the server include the required CRLF trailer, or patch the client to enforce this validation and break out of the parsing loop if the trailer is missing.

Generated by OpenCVE AI on November 3, 2026 at 16:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 03 Nov 2026 18:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-770

Tue, 03 Nov 2026 17:15:00 +0000

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

Tue, 03 Nov 2026 15:15:00 +0000

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'}


Subscriptions

Eclipse Vert.x
Eclipse Foundation Vert.x
cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published:

Updated: 2026-11-03T18:04:57.987Z

Reserved: 2026-10-28T11:32:50.242Z

Link: CVE-2026-118488

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-11-03T15:17:24.647

Modified: 2026-11-03T18:17:54.760

Link: CVE-2026-118488

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-03T17:00:16Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-789

    Memory Allocation with Excessive Size Value