NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2026-130176 — amqtt

HIGHFix: Yakifo/amqtt@2755fd8

CVE-2026-130176 is a high-severity (CVSS 7.5) CWE-401 vulnerability in amqtt. A fix is available for amqtt — see the affected versions and patch details below.

aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes

Also known asGHSA-wcqj-wx85-c75p
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍amqtt

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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 connection has closed.

Under the default configuration, anonymous clients can exploit the vulnerability without credentials. When authentication is enabled, any authenticated client permitted to initiate QoS 2 message flows may still be able to exploit it. Authentication alone is therefore not a sufficient mitigation.

  • Ecosystem: pip
  • Package: amqtt
  • Affected versions: >= 0.11.0, <= 0.12.0

The vulnerable code is present in the v0.11.0 release commit, 352678c87e50e501a8a5bb91fab73c9400fa046c, and remained present on the main branch as of 5ebbf366f6b79ab12a06f426ffd18ff28954e4ea. Versions before 0.11.0 were not evaluated.

This is a denial-of-service vulnerability only. No confidentiality or integrity impact has been identified. Successful exploitation causes degradation and eventual loss of availability through memory exhaustion.

Patches

The issue will be been patched in the v0.12.1 released version; all users should upgrade.

The completed fix:

  • Apply transaction expiration handling consistently to incomplete QoS 1 and QoS 2 message flows
  • Expire abandoned QoS 2 state when the associated transaction does not complete within the configured timeout
  • Release the associated message state and packet identifiers when the transaction expires
  • Prevent disconnected clients from leaving incomplete QoS 2 transactions resident in broker memory indefinitely

The fixing commit is 2755fd801a6f95e9b73e11116948b57a95348466

Workarounds

Administrators who cannot immediately upgrade should limit the ability of untrusted clients to create large numbers of incomplete QoS 2 transactions.

Where application requirements permit, preventing untrusted clients from using QoS 2 provides the strongest temporary mitigation.

Connection and request rate limiting at a reverse proxy, load balancer, firewall, or other network layer can reduce the rate at which an attacker creates abandoned transactions, but does not eliminate the underlying vulnerability. An attacker able to continue creating incomplete QoS 2 transactions can still cause memory usage to increase over time.

Administrators should also monitor broker memory consumption and configure appropriate process or container memory limits to prevent exhaustion of host resources. Restarting the broker may reclaim abandoned state and restore availability, but the broker remains vulnerable until the patched version is installed.

MQTT Keep Alive limits are not a sufficient mitigation because the vulnerable state persists after the client connection has already terminated.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIamqtt≥ 0.11.0&&< 0.12.10.12.1pip install --upgrade 'amqtt==0.12.1'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amqtt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update amqtt to 0.12.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-130176 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### 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 handli
O3 Security · Impact-Aware SCA

Is CVE-2026-130176 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2026-130176: amqtt DoS — Fixed in 0.12.1