CVE-2026-130176 json
aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes
published 2mo ago modified yesterday also EUVD-2026-130690 , GHSA-wcqj-wx85-c75p
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- pypi amqtt 0.12.1
- github.com/Yakifo/amqtt@2755fd8 commit
- github.com/Yakifo/amqtt@64a6f8c commit
- github.com/Yakifo/amqtt#404 pull request
- github.com/Yakifo/amqtt/releases/tag/v0.12.1 release
Is CVE-2026-130176 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-21).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | amqtt | >=0.11.0, <0.12.1 |
0.12.1 |
Affected products
- Yakifo amqtt
Classification
References
-
github.com
/Yakifo/amqtt/pull/404
web
-
github.com
/Yakifo/amqtt/commit/2755fd801a6f95e9b73e11116948b57a95348466
web
-
github.com
/Yakifo/amqtt/commit/64a6f8c3ebc47640f2e092885c1d504c8f34f1af
web
-
github.com
/Yakifo/amqtt/security/advisories/GHSA-wcqj-wx85-c75p
web, advisory
-
github.com
/Yakifo/amqtt/releases/tag/v0.12.1
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-130176
advisory
-
github.com
/Yakifo/amqtt
package
Sources
- CVE List CVE-2026-130176
- GitHub Advisory GHSA-wcqj-wx85-c75p
- NVD CVE-2026-130176
- Maintainer advisory GHSA-wcqj-wx85-c75p
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of Yakifo/amqtt published their own advisory on GitHub. Reviewed sources take precedence over it.