aMQTT denial of service via memory leak in QoS 2 handshakes
Affects amqtt 0.11.0 through 0.12.0 when a client begins a QoS 2 transaction and disconnects before the handshake completes. Fixed in 0.12.1.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.12.1
- Who is exposed
- Default setups
Summary
The Yakifo amqtt MQTT broker and client can be forced to exhaust memory until the process terminates, causing a denial of service. A remote attacker can trigger this over the network without logging in by repeatedly starting QoS 2 message flows and disconnecting before they complete.
Written by a model
Original description
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.
Who should check
Teams running the amqtt MQTT broker or client library, versions 0.11.0 through 0.12.0, with or without authentication enabled.
Not fixed by: Rate limiting at a proxy or firewall does not eliminate the underlying vulnerability.
“Affected versions: >= 0.11.0, <= 0.12.0”
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 0.12.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130176 (aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130176 (entry last updated 2026-11-19):
Affected:
- Yakifo amqtt: from 0.11.0, fixed in 0.12.1
Fixed versions: 0.12.1.
Conditions (all must be true for the bug to be hit):
- Affected versions are >= 0.11.0 through 0.12.0 of amqtt. (source: https://github.com/Yakifo/amqtt/security/advisories/GHSA-wcqj-wx85-c75p)
- A client begins a QoS 2 transaction and disconnects before the handshake completes. (source: https://github.com/Yakifo/amqtt/security/advisories/GHSA-wcqj-wx85-c75p)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130176 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130176 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Yakifo/amqtt/security/advisories/GHSA-wcqj-wx85-c75p
- https://github.com/Yakifo/amqtt/pull/404
- https://github.com/Yakifo/amqtt/commit/2755fd801a6f95e9b73e11116948b57a95348466
- https://github.com/Yakifo/amqtt/commit/64a6f8c3ebc47640f2e092885c1d504c8f34f1af
- https://github.com/Yakifo/amqtt/releases/tag/v0.12.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130176
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130176"}.Affected versions
- Yakifo amqttFrom 0.11.0 · fixed in 0.12.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Yakifo/amqtt · Advisory GHSA-wcqj-wx85-c75p |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130176 |
| Record | NVD · CVE-2026-130176 |
| Other links 4 | |
| Repository | GitHub · Yakifo/amqtt · Pull request #404 |
| Repository | GitHub · Yakifo/amqtt · Commit 2755fd80 |
| Repository | GitHub · Yakifo/amqtt · Commit 64a6f8c3 |
| Repository | GitHub · Yakifo/amqtt · Release v0.12.1 |
Questions about CVE-2026-130176
Is CVE-2026-130176 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Broker memory grows without bound from retained incomplete QoS 2 state when a client begins a QoS 2 transaction and disconnects before the handshake completes. Exhausted memory can terminate the broker process and cause loss of availability. No confidentiality or integrity impact is identified.
Source: github.com
Which versions are affected by CVE-2026-130176?
amqtt: from 0.11.0 before 0.12.1.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 0.11.0 through 0.12.0 of amqtt are affected, and the trigger is a client that begins a QoS 2 transaction and disconnects before the handshake completes. To check a installation, look at the installed amqtt version and compare it with that range.
Source: github.com
How do I fix CVE-2026-130176?
Upgrade amqtt to 0.12.1, the fixed version listed for this range.
Source: github.com
Related
- CVE-2026-104199aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
- CVE-2026-124539JSON::XS versions before 4.05 for Perl leak the decoded key of an object rejected for a missing colon in decode_hv
- CVE-2026-130732Traefik from 2.11.58 before 2.11.61 Denial of Service via NTLM/Negotiate Headers
- CVE-2026-106137ClassFactory Race Condition and Retained Assembly Memory in Telerik UI for ASP.NET MVC
- CVE-2026-80322Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
- CVE-2026-120804Credential-handle retention via missing flag set in Windows Kerberos auth handler
No corrections so far. Something wrong on this page? Report an error.