<?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:51 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-61547 — rabbitmq-c: Heap Buffer Overflow in amqp_send_frame() When Serializing Oversized AMQP_FRAME_BODY</title>
      <link>https://db.gcve.eu/vuln/cve-2026-61547</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, a heap buffer overflow exists in rabbitmq-c when the public amqp_send_frame() API is used to serialize an oversized AMQP_FRAME_BODY. The issue occurs because amqp_frame_to_bytes() copies frame.payload.body_fragment.len bytes into the connection outbound buffer without validating that the body fragment fits within the allocated frame buffer. An application that passes an oversized body frame to amqp_send_frame() can trigger a heap out-of-bounds write, resulting in process crash and memory corruption. 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, a heap buffer overflow exists in rabbitmq-c when the public amqp_send_frame() API is used to serialize an oversized AMQP_FRAME_BODY. The issue occurs because amqp_frame_to_bytes() copies frame.payload.body_fragment.len bytes into the connection outbound buffer without validating that the body fragment fits within the allocated frame buffer. An application that passes an oversized body frame to amqp_send_frame() can trigger a heap out-of-bounds write, resulting in process crash and memory corruption. 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-61547</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>
