Yakifo aMQTT
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, _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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.11.0, < 0.12.1
Fixed in 0.12.1
Mitigation
Upgrade amqtt to 0.12.1 or later.
References
- Vendor advisory github.com/Yakifo/amqtt/security/advisories/GH…
- Patch github.com/Yakifo/amqtt/pull/404
- Patch github.com/Yakifo/amqtt/commit/2755fd801a6f95e…
2 more
Timeline
Days relative to CVE publicationFirst public PoC 1.1 days after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-130176 (created 20 Nov 2026, found by us: 20 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| googlesky/CVE-2026-130176 | 20 Nov 2026 +1.1 d | 20 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.