CVE-2026-118487: Eclipse Vert.x STOMP FrameParser heap exhaustion

CVE-2026-118487 · Severity: high · CVSS 7.5 · Published 2026-11-03

Eclipse Vert.x is a reactive application framework used to build networked services. The STOMP protocol handler in vertx-stomp fails to limit the size of incoming message frames, allowing a malicious client or server to send continuous data without line breaks. An attacker can exploit this to exhaust server memory, crashing the application and causing complete service unavailability.

Technologies: Eclipse Vert.X. Vendors: Eclipse.

Quick answers

Is CVE-2026-118487 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-118487 being exploited in the wild.
How severe is CVE-2026-118487?
High severity, with a CVSS score of 7.5, published 3 November 2026.
Which products and versions are affected?
Eclipse Vert.X 4.0.0 to 4.5.35, 5.0.0 to 5.2.2.
Is there a fix for CVE-2026-118487?
Yes: fixed in 4.5.36, 5.2.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118487 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-118487?
Check whether you run Eclipse Vert.X at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: 4.5.36, 5.2.3

Technical details

The FrameParser in vertx-stomp creates a RecordParser without setting maxRecordSize, causing unbounded accumulation of data when a peer streams bytes continuously without newline characters (CWE-770: Allocation of Resources Without Limits or Throttling). Both STOMP server and client implementations are affected via network-based attack; clients can be exploited by malicious servers before or after authentication, and servers can be exploited by malicious clients without authentication. Sustained byte streaming exhausts JVM heap memory and crashes the process, causing denial of service.

Affected products

  • Eclipse Vert.x 4.0.0 to 4.5.35, 5.0.0 to 5.2.2

Timeline

  • 2026-11-03: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.