<?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-20T22:01:14.910477+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/bit-rabbitmq-2024-51988</id>
    <title>BIT-rabbitmq-2024-51988 — HTTP API's queue deletion endpoint does not verify that the user has a required permission</title>
    <updated>2026-10-20T22:01:14.914545+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: rabbitmq</p>
<p>RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. In affected versions queue deletion via the HTTP API was not verifying the `configure` permission of the user. Users who had all of the following: 1. Valid credentials, 2. Some permissions for the target virtual host &amp; 3. HTTP API access. could delete queues it had no (deletion) permissions for. This issue has been addressed in version 3.12.11 of the open source rabbitMQ release and in versions 1.5.2, 3.13.0, and 4.0.0 of the tanzu release. Users are advised to upgrade. Users unable to upgrade may disable management plugin and use, for example, Prometheus and Grafana for monitoring.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-rabbitmq-2024-51988"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-199801</id>
    <title>EUVD-2026-199801</title>
    <updated>2026-10-20T22:01:14.914611+00:00</updated>
    <content>EUVD-2026-199801</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-199801"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-51988</id>
    <title>fkie_cve-2024-51988</title>
    <updated>2026-10-20T22:01:14.914627+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. In affected versions queue deletion via the HTTP API was not verifying the `configure` permission of the user. Users who had all of the following: 1. Valid credentials, 2. Some permissions for the target virtual host &amp; 3. HTTP API access. could delete queues it had no (deletion) permissions for. This issue has been addressed in version 3.12.11 of the open source rabbitMQ release and in versions 1.5.2, 3.13.0, and 4.0.0 of the tanzu release. Users are advised to upgrade. Users unable to upgrade may disable management plugin and use, for example, Prometheus and Grafana for monitoring.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-51988"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-pj33-75x5-32j4</id>
    <title>GHSA-pj33-75x5-32j4 — RabbitMQ HTTP API's queue deletion endpoint does not verify that the user has a required permission</title>
    <updated>2026-10-20T22:01:14.914662+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Hex: rabbit_common</p>
<p>### Summary</p>
<p>Queue deletion via the HTTP API was not verifying the `configure` permission of the user.</p>
<p>### Impact</p>
<p>Users who had all of the following:</p>
<p>1. Valid credentials
2. Some permissions for the target virtual host
3. HTTP API access</p>
<p>could delete queues it had no (deletion) permissions for.</p>
<p>### Workarounds</p>
<p>Disable management plugin and use, for example, [Prometheus and Grafana](https://www.rabbitmq.com/docs/prometheus) for monitoring.</p>
<p>### OWASP Classification</p>
<p>OWASP Top10 A01:2021 – Broken Access Control</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-pj33-75x5-32j4"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-51988</id>
    <title>Withdrawn: UBUNTU-CVE-2024-51988</title>
    <updated>2026-10-20T22:01:14.914701+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> Ubuntu:20.04:LTS: rabbitmq-server, Ubuntu:22.04:LTS: rabbitmq-server, Ubuntu:24.04:LTS: rabbitmq-server</p>
<p>RabbitMQ is a feature rich, multi-protocol messaging and streaming broker. In affected versions queue deletion via the HTTP API was not verifying the `configure` permission of the user. Users who had all of the following: 1. Valid credentials, 2. Some permissions for the target virtual host &amp; 3. HTTP API access. could delete queues it had no (deletion) permissions for. This issue has been addressed in version 3.12.11 of the open source rabbitMQ release and in versions 1.5.2, 3.13.0, and 4.0.0 of the tanzu release. Users are advised to upgrade. Users unable to upgrade may disable management plugin and use, for example, Prometheus and Grafana for monitoring.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-51988"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3357</id>
    <title>WID-SEC-W-2024-3357 — RabbitMQ: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
    <updated>2026-10-20T22:01:14.914728+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in RabbitMQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen und Daten zu manipulieren.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3357"/>
  </entry>
</feed>
