<?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 11:33:46 +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-67418</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-67418</link>
      <description>&lt;p&gt;RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, the MQTT 5 parser in deps/rabbitmq_mqtt/src/rabbit_mqtt_packet.erl accepts Request-Problem-Information on PUBLISH packets even though the property is valid only for CONNECT. An authenticated publisher with topic write permission can cause the broker to store and route that inapplicable property to a separately authenticated matching subscriber. When the subscriber path serializes the outbound PUBLISH, serialise_prop/2 has no matching clause, and the uncontained function_clause exception closes the victim MQTT or Web MQTT connection. The publisher connection and broker remain available, and queued replay, retained-message persistence, and broker-wide denial of service were not established. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RabbitMQ is a messaging and streaming broker. From 3.13.0 until 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5, the MQTT 5 parser in deps/rabbitmq_mqtt/src/rabbit_mqtt_packet.erl accepts Request-Problem-Information on PUBLISH packets even though the property is valid only for CONNECT. An authenticated publisher with topic write permission can cause the broker to store and route that inapplicable property to a separately authenticated matching subscriber. When the subscriber path serializes the outbound PUBLISH, serialise_prop/2 has no matching clause, and the uncontained function_clause exception closes the victim MQTT or Web MQTT connection. The publisher connection and broker remain available, and queued replay, retained-message persistence, and broker-wide denial of service were not established. This issue is fixed in versions 3.13.19, 4.0.24, 4.1.15, 4.2.10, and 4.3.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-67418</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-67418 — RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-67418</link>
      <description>msrc_CVE-2026-67418</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-67418</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>
