CVE-2026-118487
highIn 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…
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
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/vert-x3/vertx-stomp/security/advisories/GHSA-cchp-hff9-j7q7 emo@eclipse.org
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/521 emo@eclipse.org
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/864 emo@eclipse.org
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/864 134c704f-9b21-4f2e-91b3-4a467353bcc0

