32 matches found
EUVD-2026-130690
aMQTT: Denial of Service DoS via Memory Leak in Unmanaged QoS 2 Session Handshakes...
CVE-2026-130176
aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.12.1, the QoS 2 transaction handler in amqtt/mqtt/protocol/handler.py, handleqos2messageflow, can retain transaction state and packet identifiers when a client disconnects before the handshake completes, unlike QoS 1 flows that...
CVE-2026-130176 aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.12.1, the QoS 2 transaction handler in amqtt/mqtt/protocol/handler.py, handleqos2messageflow, can retain transaction state and packet identifiers when a client disconnects before the handshake completes, unlike QoS 1 flows that...
CVE-2026-130176 aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.12.1, the QoS 2 transaction handler in amqtt/mqtt/protocol/handler.py, handleqos2messageflow, can retain transaction state and packet identifiers when a client disconnects before the handshake completes, unlike QoS 1 flows that...
CVE-2026-130176
The aMQTT open source MQTT broker and client (versions 0.11.0 through 0.12.1 ) is vulnerable to a Denial of Service (DoS) due to a memory leak in the QoS 2 transaction handler located at amqtt/mqtt/protocol/handler.py within the _handle_qos2_message_flow() function. The root cause is that the han...
PT-2026-152145
aMQTT is an open source MQTT broker and client. From 0.11.0 until 0.12.1, the QoS 2 transaction handler in amqtt/mqtt/protocol/handler.py, handle qos2 message flow, can retain transaction state and packet identifiers when a client disconnects before the handshake completes, unlike QoS 1 flows tha...
CVE-2026-102464
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...
CVE-2026-102464
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...
CVE-2026-102464
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...
EUVD-2026-101936
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...
CVE-2026-102464
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...
CVE-2026-102464
The io.vertx:vertx-mqtt component in Eclipse Vert.x versions [4.0.0, 4.5.34], [5.0.0, 5.0.12], [5.1.0, 5.1.9], and [5.2.0, 5.2.0] is vulnerable to unbounded memory growth . The MqttClient stores inbound QoS 2 PUBLISH messages in an internal map (qos2inbound ) while awaiting a PUBREL packet. Becau...
CVE-2026-102464
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...
CVE-2026-102464: Allocation of Resources Without Limits or Throttling
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...
PT-2026-114830
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...
CVE-2026-8741
A vulnerability has been found in EMQX up to 6.2.0. This affects an unknown function of the file apps/emqx/src/emqxpersistentsessionds.erl of the component QoS 2 PUBLISH Packet Handler. Such manipulation leads to race condition. The attack may be performed from remote. A high complexity level is...
CVE-2026-8741: Concurrent Execution using Shared Resource with Improper Synchronization
A vulnerability has been found in EMQX up to 6.2.0. This affects an unknown function of the file apps/emqx/src/emqxpersistentsessionds.erl of the component QoS 2 PUBLISH Packet Handler. Such manipulation leads to race condition. The attack may be performed from remote. A high complexity level is...
EUVD-2023-32063
Malicious code in bioql PyPI...
MGASA-2025-0106 Updated mosquitto packages fix security vulnerability
The broker in Eclipse Mosquitto 1.3.2 through 2.x before 2.0.16 has a memory leak that can be abused remotely when a client sends many QoS 2 messages with duplicate message IDs, and fails to respond to PUBREC commands. This occurs because of mishandling of EAGAIN from the libc send function...
Updated mosquitto packages fix security vulnerability
The broker in Eclipse Mosquitto 1.3.2 through 2.x before 2.0.16 has a memory leak that can be abused remotely when a client sends many QoS 2 messages with duplicate message IDs, and fails to respond to PUBREC commands. This occurs because of mishandling of EAGAIN from the libc send function...