CVE-2026-102464: Vulnerability in Eclipse Foundation Eclipse Vert.x
Description
In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], the Eclipse Vert.x MQTT (vertx-mqtt) MqttClient stores every inbound QoS 2 PUBLISH message received from the broker in an internal map (qos2inbound) while awaiting the corresponding PUBREL packet to complete the QoS 2 handshake. This map has no size limit; the maxInflightQueue option is enforced only on the outbound publish path and does not constrain inbound message retention. A malicious or compromised MQTT broker can exploit this by sending QoS 2 PUBLISH messages with distinct packet identifiers and withholding the PUBREL responses. Each incomplete handshake causes the client to retain the full publish message (topic, payload, and metadata) indefinitely, leading to unbounded memory growth in the Vert.x process. This can degrade the MQTT-consuming application or cause out-of-memory termination. The impacted component is io.vertx:vertx-mqtt.
CVSS v4.0
Score 8.2high
Affected software
Eclipse Foundation
Eclipse Vert.x
pkg:maven/io.vertx/vertx-mqttRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Eclipse Vert.x MQTT client (vertx-mqtt) versions >=4.0.0 <=4.5.34, >=5.0.0 <=5.0.12, >=5.1.0 <=5.1.9, and =5.2.0, the internal map (qos2inbound) that holds inbound QoS 2 PUBLISH messages awaiting PUBREL packets has no size limit. The maxInflightQueue option only limits outbound messages and does not constrain inbound message retention. A malicious or compromised MQTT broker can send many QoS 2 PUBLISH messages with unique packet identifiers and withhold PUBREL responses, causing the client to retain all these messages indefinitely. This leads to unbounded memory consumption, which can degrade performance or cause out-of-memory termination of the Vert.x process.
Potential Impact
The vulnerability allows a malicious or compromised MQTT broker to cause unbounded memory growth in the Eclipse Vert.x MQTT client by sending numerous QoS 2 PUBLISH messages without completing the QoS 2 handshake. This can degrade the MQTT-consuming application or cause it to terminate due to out-of-memory conditions. There is no indication of remote code execution or data leakage, but denial of service via resource exhaustion is the primary impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider limiting exposure to untrusted MQTT brokers or implementing external controls to detect and block abnormal QoS 2 message patterns. No official fix or patch links are currently provided.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- eclipse
- Date Reserved
- 2026-09-29T08:30:06.333Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad090022cdf04f656196485
Added to database: 10/15/2026, 08:34:10 UTC
Last enriched: 10/15/2026, 08:48:49 UTC
Last updated: 10/15/2026, 19:00:27 UTC
Views: 16
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.