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: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

Remediation

No vendor fix or workaround currently provided.

Additional remediation guidance may be available on OpenCVE Cloud.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

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

Type Values Removed Values Added
Metrics ssvc

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


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

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

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