<?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, 17 Oct 2026 07:41:28 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1125 — De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1125</link>
      <description>certfr-2026-avi-1125</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1125</guid>
    </item>
    <item>
      <title>fkie_cve-2026-67414</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-67414</link>
      <description>&lt;p&gt;RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not the aggregate arrays in a frame. After completing SASL authentication, a low-privilege client can send an ordinary frame containing many individually permitted arrays, causing a small frame to expand into a very large reader-process heap before later frame validation or authorization. Because deps/rabbit/src/rabbit_amqp_reader.erl clears the pre-authentication max_heap_size guard after login, repeated or concurrent frames can trigger the node-wide memory alarm, block publishers, or exhaust broker memory. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.24, 4.1.15, 4.2.10, and 4.3.4, deps/amqp10_common/src/amqp10_binary_parser.erl materializes each element of AMQP 1.0 arrays whose shared constructor has zero width, while limiting only the number of elements in each array and not the aggregate arrays in a frame. After completing SASL authentication, a low-privilege client can send an ordinary frame containing many individually permitted arrays, causing a small frame to expand into a very large reader-process heap before later frame validation or authorization. Because deps/rabbit/src/rabbit_amqp_reader.erl clears the pre-authentication max_heap_size guard after login, repeated or concurrent frames can trigger the node-wide memory alarm, block publishers, or exhaust broker memory. This issue is fixed in versions 4.0.24, 4.1.15, 4.2.10, and 4.3.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-67414</guid>
    </item>
    <item>
      <title>RHSA-2026:82703 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2026:82703</link>
      <description>&lt;p&gt;rabbitmq-server: rabbitmq-server: Denial of Service via memory exhaustion in AMQP parser rabbitmq-server: rabbitmq-server: Denial of Service via improper AMQP message descriptor validation rabbitmq-server: rabbitmq-server: Denial of Service via invalid MQTT PUBLISH property&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;rabbitmq-server: rabbitmq-server: Denial of Service via memory exhaustion in AMQP parser rabbitmq-server: rabbitmq-server: Denial of Service via improper AMQP message descriptor validation rabbitmq-server: rabbitmq-server: Denial of Service via invalid MQTT PUBLISH property&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2026:82703</guid>
    </item>
  </channel>
</rss>
