<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T23:16:55.372054+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-335867</id>
    <title>EUVD-2026-335867</title>
    <updated>2026-10-03T23:16:55.578355+00:00</updated>
    <content>EUVD-2026-335867</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-335867"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-57216</id>
    <title>fkie_cve-2026-57216</title>
    <updated>2026-10-03T23:16:55.578397+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-57216"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-57216</id>
    <title>msrc_CVE-2026-57216 — RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-…</title>
    <updated>2026-10-03T23:16:55.578432+00:00</updated>
    <content>msrc_CVE-2026-57216</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-57216"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-3940</id>
    <title>OESA-2026-3940 — rabbitmq-server security update</title>
    <updated>2026-10-03T23:16:55.578453+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: rabbitmq-server</p>
<p>RabbitMQ is an implementation of AMQP, the emerging standard for high performance enterprise messaging. The RabbitMQ server is a robust and scalable implementation of an AMQP broker.

Security Fix(es):</p>
<p>RabbitMQ all versions prior to 3.8.16 are prone to a denial of service vulnerability due to improper input validation in AMQP 1.0 client connection endpoint. A malicious user can exploit the vulnerability by sending malicious AMQP messages to the target RabbitMQ instance having the AMQP 1.0 plugin enabled.(CVE-2021-22116)</p>
<p>RabbitMQ is a messaging and streaming broker. Prior to 4.2.5, the RabbitMQ management UI renders the x-internal-purpose queue or exchange argument into an HTML title attribute without proper escaping on the Queues and Exchanges pages, allowing a user with permission to declare a queue or exchange to execute JavaScript in another user&amp;apos;s browser. This issue is fixed in version 4.2.5.(CVE-2026-57214)</p>
<p>RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues can be accepted at bind and route time but are missing from Khepri-backed deletion checks, leaving persistent route entries after unbind. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.(CVE-2026-57215)</p>
<p>RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, AMQP 0-9-1, AMQP 1.0, and Stream Protocol auth…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-3940"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:21903-1</id>
    <title>openSUSE-SU-2026:21903-1 — Security update for rabbitmq-server</title>
    <updated>2026-10-03T23:16:55.578499+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for rabbitmq-server</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:21903-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:35939</id>
    <title>RHSA-2026:35939 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
    <updated>2026-10-03T23:16:55.578523+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>rabbitmq: RabbitMQ: Information disclosure via path validation bypass in management plugin rabbitmq-server: RabbitMQ: Denial of Service via oversized JSON bodies in HTTP API rabbitmq-server: RabbitMQ: Information Disclosure via Cross-Site Scripting in Federation Management RabbitMQ: RabbitMQ: Cross-site Scripting in management UI allows arbitrary JavaScript execution RabbitMQ: RabbitMQ: Persistent foreign bindings allow unauthorized message routing rabbitmq: RabbitMQ: Authentication bypass allows remote connection for loopback-restricted users via incorrect loopback check rabbitmq: RabbitMQ: Authorization bypass allows unauthorized topic writes and binds during metadata-store failures rabbitmq-server: RabbitMQ: Information disclosure due to improper consumer reauthorization RabbitMQ: RabbitMQ: OAuth 2 client secret disclosure via obsolete API endpoint rabbitmq-server: RabbitMQ: Denial of Service via oversized stream frames RabbitMQ: RabbitMQ: Information disclosure via authorization bypass in AMQP 0-9-1 operations</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:35939"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:23859-1</id>
    <title>SUSE-SU-2026:23859-1 — Security update for rabbitmq-server</title>
    <updated>2026-10-03T23:16:55.578598+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for rabbitmq-server</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:23859-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-57216</id>
    <title>UBUNTU-CVE-2026-57216</title>
    <updated>2026-10-03T23:16:55.578618+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: rabbitmq-server, Ubuntu:18.04:LTS: rabbitmq-server, Ubuntu:20.04:LTS: rabbitmq-server, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: rabbitmq-server, Ubuntu:26.04:LTS: rabbitmq-server</p>
<p>RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-57216"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2079</id>
    <title>WID-SEC-W-2026-2079 — RabbitMQ: Mehrere Schwachstellen</title>
    <updated>2026-10-03T23:16:55.578648+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in RabbitMQ ausnutzen, um einen Denial-of-Service-Zustand zu verursachen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder vertrauliche Informationen offenzulegen, was möglicherweise weitere Angriffe ermöglicht.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2079"/>
  </entry>
</feed>
