amqtt discloses remote denial-of-service flaw affecting versions 0.11.0 to 0.12.0

  • amqtt
  • MQTT QoS 2
  • memory leak
  • denial of service

Incomplete QoS 2 transactions remain in memory after clients disconnect

Version 0.12.1 fixes the flaw with transaction expiration handling

The amqtt project disclosed a memory-leak vulnerability in amqtt that can let remote attackers cause a denial of service. The advisory was published on November 20, 2026.

The flaw affects amqtt versions 0.11.0 through 0.12.0. When a client disconnects before completing an MQTT Quality of Service 2 (QoS 2) transaction—a message-delivery handshake—the broker leaves the transaction in memory indefinitely. Repeated incomplete transactions can cause unbounded memory growth and potentially terminate the broker process.

The advisory says QoS 1 transactions already had a five-second timeout, but QoS 2 transactions lacked that protection. Version 0.12.1 resolves the issue by applying consistent transaction-expiration handling.