CVE-2026-118488

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

  • Medium 5.9

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.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
eclipse
EPSS
0.433% likely to be exploited in the next 30 days, higher than 38.13% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.9CVSS 3.1, Mediumfrom the CNA (eclipse)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Eclipse FoundationEclipse Vert.x
  • Default status: unaffected
  • 4.0.0 up to and including 4.5.35 (affected)
  • 5.0.0 up to and including 5.2.2 (affected)

Timeline

  1. 3 Nov 2026 Published

Weakness

References