CVE-2026-118487: high-severity vulnerability in Eclipse Vert.x
Heap exhaustion via unbounded line accumulation in Vert.x STOMP FrameParser
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.7%
In Eclipse Vert.x versions [4.0.0, 4.5.35] or [5.0.0, 5.2.2], the `FrameParser` in vertx-stomp creates a `RecordParser` without setting `maxRecordSize`, so any peer that streams bytes continuously without a newline character causes the parser to accumulate data indefinitely. Both the STOMP server and the STOMP client are affected: a malicious server can exploit this against a connecting client, and a malicious client can exploit this against a server before or after authentication. Sustained byte streaming exhausts JVM heap memory, crashing the affected process and causing a complete denial of service.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
Eclipse Foundation · Eclipse Vert.xRelated CVEs — Eclipse Vert.x
In the same product, most dangerous first.
CVE-2024-8391MEDIUMEclipse Vert.x gRPC server does not limit the maximum message sizeEPSS 0.6%CVE-2026-102469CRITICALCVE-2026-102469EPSS 0.5%CVE-2026-118488MEDIUMHeap exhaustion via unbounded simple string or bulk string allocation in Vert.x Redis clientEPSS 0.4%CVE-2026-102461HIGHCVE-2026-102461EPSS 0.4%CVE-2026-118489HIGHCachingWebClient shares user-specific HTTP responses across users via the shared cache tierEPSS 0.3%CVE-2026-102479HIGHCVE-2026-102479EPSS 0.3%