<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T06:31:16.363339+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-130176</id>
    <title>fkie_cve-2026-130176</title>
    <updated>2026-11-21T06:31:16.364932+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-130176"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-wcqj-wx85-c75p</id>
    <title>GHSA-wcqj-wx85-c75p — aMQTT: Denial of Service (DoS) via Memory Leak in Unmanaged QoS 2 Session Handshakes</title>
    <updated>2026-11-21T06:31:16.365023+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: amqtt</p>
<p>### Impact</p>
<p>`amqtt` is vulnerable to a remote denial of service caused by incomplete MQTT QoS 2 transactions remaining allocated after the associated client disconnects.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>Successful exploitation can cause:</p>
<p>* 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</p>
<p>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 connect…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-wcqj-wx85-c75p"/>
  </entry>
</feed>
