CVE-2026-130176: high-severity vulnerability in Yakifo amqtt
aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.5epss 0.6%
from disclosure to weapon1 day
Published on NVDNov 19
1st PoC+1d
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
Yakifo · amqttpublic PoCs found — 1
githubgithub.com/googlesky/CVE-2026-130176★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Yakifo amqtt
In the same product, most dangerous first.
References
https://github.com/Yakifo/amqtt/commit/2755fd801a6f95e9b73e11116948b57a95348466https://github.com/Yakifo/amqtt/commit/64a6f8c3ebc47640f2e092885c1d504c8f34f1afhttps://github.com/Yakifo/amqtt/pull/404https://github.com/Yakifo/amqtt/releases/tag/v0.12.1https://github.com/Yakifo/amqtt/security/advisories/GHSA-wcqj-wx85-c75p