CVE-2026-102464
Eclipse Vert.x: denial of service
- Risk score
- 40/100
- CVSS
- 5.9 v3.1
- Exploit chance (30 days)
- 0.3%
- Published
- 15 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 hand…
- Affected
- Eclipse Vert.x
- Fix
- Apply the vendor's security update; see the linked advisory.
- Exploitation
- No known exploitation
Story map
At a glance
Eclipse Vert.x: Yellow, plan it in. 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 PostgreSQL message decoder reads the 4-byte message length field from the PostgreSQL wire protocol without any maximum validation. A malicious, compromised, or man-in-the-middle PostgreSQL server can send a message hea…
The flaws
- CVE-2026-102464: Denial of service (CVSS 5.9 · EPSS 0%)
- CVE-2026-103223: Denial of service (CVSS 5.9 · EPSS 0%)
- CVE-2026-102465: Denial of service (CVSS 5.9 · EPSS 0%)
- CVE-2026-102469: Unsafe deserialisation can lead to remote code execution (CVSS 5.9 · EPSS 0%)
The fix
Fix: Apply the vendor's security update; see the linked advisory.
Who is exposed: Eclipse Vert.x
Where it stands
- No known exploitation
Connects to
- Same weakness: Denial of service (CWE-770). 205 other warnings in 30 days
- Same product: Earlier Eclipse Vert.x warnings. 11 in the last 90 days
Why it is Yellow
- CVSS 5.9 medium
References
Original 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.
Last activity 15 Oct 2026. Patch Forecast updates every hour.