Skip to main content
VulnerabilityPublished

CVE-2026-130176: aMQTT · Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes

Affects amqttSource GCVE Database

0
Compare
Authoritative record:CVE-2026-130176· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 0.12.1 soon.

Data as of 20 Nov 2026, 15:53 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 0.12.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade amqtt to 0.12.1.

Affected software

ProductAffectedFixed in
PyPIamqttAffected
  • >=0.11.0 <0.12.1
Fixed in
  • 0.12.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in amqtt version 0.12.1 that fixes the vulnerability by applying transaction expiration handling to incomplete QoS 2 transactions. All users should upgrade to this version. Until then, administrators should limit untrusted clients from creating large numbers of incomplete QoS 2 transactions, disable QoS 2 usage for untrusted clients if possible, and implement connection and request rate limiting at network layers. Monitoring broker memory consumption and setting process or container memory limits can help prevent host resource exhaustion. Restarting the broker reclaims memory but does not fix the underlying vulnerability. MQTT Keep Alive settings do not mitigate this issue.

Description

The amqtt package versions 0.11.0 through 0.12.0 contain a denial-of-service vulnerability due to a memory leak in the handling of incomplete MQTT QoS 2 transactions. When clients initiate QoS 2 handshakes but disconnect before completion, the broker retains transaction state indefinitely, causing unbounded memory growth. This can lead to broker process termination and loss of availability. The issue is patched in version 0.12.1.

References

Community reviews

Loading reviews…