Vulnerability in Yakifo Amqtt
CVE-2026-130176
- CVSS v3
- 7.5 High
- Public exploits
- 1 repository
- EPSS
- 0.004 · 39.7th percentile
- Published
- 2026-11-19
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 that expire after the default five-second timeout. A remote client can repeatedly begin QoS 2 flows and disconnect without maintaining long-lived connections; anonymous clients can do this with the default configuration, while authenticated deployments remain affected when a client may initiate QoS 2 flows. The retained state grows broker memory until resource exhaustion can terminate the process; no confidentiality or integrity impact is identified. This issue is fixed in version 0.12.1.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - Privileges Required
- None
PR:N - User Interaction
- None
UI:N - Scope
- Unchanged
S:U - Confidentiality
- None
C:N - Integrity
- None
I:N - Availability
- High
A:H
EPSS exploit prediction
EPSS 0.004, 39.7th percentile (last changed ). About EPSS.
Affected products
- Yakifo Amqtt — versions >= 0.11.0, < 0.12.1
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- googlesky/CVE-2026-130176 (last pushed 2026-11-20): aMQTT 0.11.0-0.12.0: outgoing QoS2 awaited PUBREC/PUBCOMP with no timeout — abandoned handshakes retain broker task/session/inflight state indefinitely, anonymous memory-exhaustion DoS. Real broker 0…