<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 15:54:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-59986 — rabbitmq-c: amqp_decode_bytes size_t integer overflow bypasses bounds check on 32-bit (OOB read)</title>
      <link>https://db.gcve.eu/vuln/cve-2026-59986</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; alanxz rabbitmq-c&lt;/p&gt;
&lt;p&gt;rabbitmq-c is a C-language AMQP client library for RabbitMQ. Prior to version 0.17.0, the bounds check (*offset = o + len) &amp;lt;= encoded.len overflows when o + len &amp;gt; SIZE_MAX on 32-bit systems. len is a uint32_t read from the AMQP wire as a BYTES/UTF8 field length. The overflow wraps the check to a small value that passes, producing a decoded amqp_bytes_t with a multi-GB .len pointing into a small frame buffer. This results in an out-of-bounds read of up to ~4GB of process memory on 32-bit systems (ARM, MIPS, x86 ILP32, embedded IoT AMQP clients). Enabling information disclosure or denial of service. Not exploitable on 64-bit systems where size_t is 64-bit. This issue has been patched in version 0.17.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; alanxz rabbitmq-c&lt;/p&gt;
&lt;p&gt;rabbitmq-c is a C-language AMQP client library for RabbitMQ. Prior to version 0.17.0, the bounds check (*offset = o + len) &amp;lt;= encoded.len overflows when o + len &amp;gt; SIZE_MAX on 32-bit systems. len is a uint32_t read from the AMQP wire as a BYTES/UTF8 field length. The overflow wraps the check to a small value that passes, producing a decoded amqp_bytes_t with a multi-GB .len pointing into a small frame buffer. This results in an out-of-bounds read of up to ~4GB of process memory on 32-bit systems (ARM, MIPS, x86 ILP32, embedded IoT AMQP clients). Enabling information disclosure or denial of service. Not exploitable on 64-bit systems where size_t is 64-bit. This issue has been patched in version 0.17.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-59986</guid>
    </item>
    <item>
      <title>USN-8724-1 — librabbitmq vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8724-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: librabbitmq, Ubuntu:Pro:16.04:LTS: librabbitmq, Ubuntu:Pro:18.04:LTS: librabbitmq, Ubuntu:Pro:20.04:LTS: librabbitmq, Ubuntu:22.04:LTS: librabbitmq, Ubuntu:24.04:LTS: librabbitmq, Ubuntu:26.04:LTS: librabbitmq&lt;/p&gt;
&lt;p&gt;It was discovered that the rabbitmq-c command-line tools only accepted
credentials on the command line, making them visible to other local users
through the process list. An attacker could possibly use this to obtain
sensitive credentials. This issue only affected Ubuntu 14.04 LTS, Ubuntu
16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2023-35789)&lt;/p&gt;
&lt;p&gt;It was discovered that rabbitmq-c did not correctly compute AMQP frame
lengths, leading to a size_t underflow. A remote attacker could possibly
use this to cause rabbitmq-c to crash, resulting in a denial of service, or
possibly expose sensitive information. This issue only affected Ubuntu
14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.
(CVE-2026-44235)&lt;/p&gt;
&lt;p&gt;It was discovered that rabbitmq-c did not properly validate the frame size
during the AMQP login handshake. A remote attacker could possibly use this
to cause a heap buffer overflow, resulting in a denial of service or
possibly the execution of arbitrary code. This issue only affected Ubuntu
14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.
(CVE-2026-44236)&lt;/p&gt;
&lt;p&gt;It was discovered that rabbitmq-c did not correctly validate the length of
decoded bytes fields, leading to an integer overflow in a bounds check on
32-bit systems. A remote attacker controlling a broker, or able to
intercept an unencrypted connection, could possibly use this to cause an
out-of-bounds read, resulting in a denial of service or the exposure of
sensitive information…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: librabbitmq, Ubuntu:Pro:16.04:LTS: librabbitmq, Ubuntu:Pro:18.04:LTS: librabbitmq, Ubuntu:Pro:20.04:LTS: librabbitmq, Ubuntu:22.04:LTS: librabbitmq, Ubuntu:24.04:LTS: librabbitmq, Ubuntu:26.04:LTS: librabbitmq&lt;/p&gt;
&lt;p&gt;It was discovered that the rabbitmq-c command-line tools only accepted
credentials on the command line, making them visible to other local users
through the process list. An attacker could possibly use this to obtain
sensitive credentials. This issue only affected Ubuntu 14.04 LTS, Ubuntu
16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS. (CVE-2023-35789)&lt;/p&gt;
&lt;p&gt;It was discovered that rabbitmq-c did not correctly compute AMQP frame
lengths, leading to a size_t underflow. A remote attacker could possibly
use this to cause rabbitmq-c to crash, resulting in a denial of service, or
possibly expose sensitive information. This issue only affected Ubuntu
14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.
(CVE-2026-44235)&lt;/p&gt;
&lt;p&gt;It was discovered that rabbitmq-c did not properly validate the frame size
during the AMQP login handshake. A remote attacker could possibly use this
to cause a heap buffer overflow, resulting in a denial of service or
possibly the execution of arbitrary code. This issue only affected Ubuntu
14.04 LTS, Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, and Ubuntu 20.04 LTS.
(CVE-2026-44236)&lt;/p&gt;
&lt;p&gt;It was discovered that rabbitmq-c did not correctly validate the length of
decoded bytes fields, leading to an integer overflow in a bounds check on
32-bit systems. A remote attacker controlling a broker, or able to
intercept an unencrypted connection, could possibly use this to cause an
out-of-bounds read, resulting in a denial of service or the exposure of
sensitive information…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8724-1</guid>
    </item>
  </channel>
</rss>
