- Severity: HIGH
- CVE: CVE-2026-130176
- Ecosystems: pip
- Packages: amqtt
### Impact
`amqtt` is vulnerable to a remote denial of service caused by incomplete MQTT QoS 2 transactions remaining allocated after the associated client disconnects.
MQTT QoS 2 uses a four-step handshake to provide exactly-once delivery. If a client begins a QoS 2 transaction but disconnects before the handshake completes, `amqtt` retains the associated transaction state and packet identifier without an expiration mechanism to remove it.
QoS 1 transactions are protected by a timeout mechanism, which defaults to 5 seconds, allowing abandoned state to be released. Equivalent timeout handling was not applied to incomplete QoS 2 transactions.
An attacker can repeatedly connect to the broker, initiate QoS 2 transactions, and disconnect before completing the handshake. Each incomplete transaction leaves state allocated in memory. Repeating this process causes broker memory consumption to grow continuously.
Successful exploitation can cause:
* Unbounded growth in broker memory usage
* Accumulation of incomplete QoS 2 transaction state
* Increasing memory pressure on the host system
* Termination of the broker process when available memory is exhausted
* Operating-system Out-Of-Memory (OOM) intervention
* Complete loss of availability for the affected broker process
Exploitation does not require maintaining long-lived connections. An attacker can create incomplete QoS 2 transactions and disconnect, leaving the broker to retain the associated state after the network connecti…
Source: GitHub Security Advisories · 2026-11-20