Eclipse Vert.x up to 4.5.35/5.2.2 RESP Parser infinite loop

Summaryinfo

A vulnerability marked as problematic has been reported in Eclipse Vert.x up to 4.5.35/5.2.2. The impacted element is an unknown function of the component RESP Parser. Performing a manipulation results in infinite loop. This vulnerability is identified as CVE-2026-118488. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in Eclipse Vert.x up to 4.5.35/5.2.2. This affects an unknown code of the component RESP Parser. The manipulation with an unknown input leads to a infinite loop vulnerability. CWE is classifying the issue as CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. This is going to have an impact on availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-118488 since 10/28/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• Eclipse

Name

• Vert.x

Version

• 4.5.0
• 4.5.1
• 4.5.2
• 4.5.3
• 4.5.4
• 4.5.5
• 4.5.6
• 4.5.7
• 4.5.8
• 4.5.9
• 4.5.10
• 4.5.11
• 4.5.12
• 4.5.13
• 4.5.14
• 4.5.15
• 4.5.16
• 4.5.17
• 4.5.18
• 4.5.19
• 4.5.20
• 4.5.21
• 4.5.22
• 4.5.23
• 4.5.24
• 4.5.25
• 4.5.26
• 4.5.27
• 4.5.28
• 4.5.29
• 4.5.30
• 4.5.31
• 4.5.32
• 4.5.33
• 4.5.34
• 4.5.35
• 5.2.0
• 5.2.1
• 5.2.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion