CVE Watchtower

CVE-2026-130176Yakifo amqtt >= 0.11.0, Missing Release of Memory after Effective Lifetime

NVDCVSS scored by security-advisories@github.com

Vulnerability 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.
Severity Level
HIGH(7.5)
Published Date
Nov 19, 2026
Last Modified
Nov 20, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
0.62%Probability
Root Weakness (CWE)
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Yakifo amqtt >= 0.11.0, < 0.12.1
Patched Versions
No patched version published yet
Until a fix ships, reduce exposure:
  • Restrict access to the affected service or interface to trusted networks.
  • Disable the affected feature if you do not need it.
  • Watch the vendor advisory for a firmware or software update.

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Yakifo amqtt >= 0.11.0, and which version.
  2. No patched version is listed yet. Limit access to the affected service to trusted networks, and disable the feature if you can.
  3. Subscribe to the vendor advisory so you learn when a fix ships.

Timeline

  • Nov 19, 2026Published
  • Nov 20, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Yakifo amqtt >= 0.11.0, CVEsYou are reading CVE-2026-130176. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 22, 2026 15:22 UTC