Debian Package Tracker
Register | Log in
Subscribe

rabbitmq-server

AMQP server written in Erlang

Choose email to subscribe with

general
  • source: rabbitmq-server (main)
  • version: 4.3.0-2
  • maintainer: Debian OpenStack (DMD)
  • uploaders: Thomas Goirand [DMD] – James Page [DMD]
  • arch: all
  • std-ver: 4.6.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 3.8.9-3+deb11u1
  • o-o-sec: 3.8.9-3+deb11u1
  • oldstable: 3.10.8-1.1+deb12u1
  • old-sec: 3.10.8-1.1+deb12u1
  • stable: 4.0.5-6+deb13u2
  • testing: 4.0.5-14
  • unstable: 4.3.0-2
versioned links
  • 3.8.9-3+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.10.8-1.1+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.0.5-6+deb13u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.0.5-14: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.3.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • rabbitmq-server
action needed
Debci reports failed tests high
  • unstable: fail (log)
    The tests ran in 2:48:01
    Last run: 2026-05-19T21:13:11.000Z
    Previous status: unknown

  • testing: pass (log)
    The tests ran in 0:01:16
    Last run: 2026-06-03T06:26:31.000Z
    Previous status: unknown

  • stable: pass (log)
    The tests ran in 0:03:20
    Last run: 2025-11-10T00:01:31.000Z
    Previous status: unknown

Created: 2026-05-19 Last update: 2026-06-04 01:00
A new upstream version is available: 4.3.1 high
A new upstream version 4.3.1 is available, you should consider packaging it.
Created: 2026-01-02 Last update: 2026-06-03 22:00
2 security issues in bookworm high

There are 2 open security issues in bookworm.

1 important issue:
  • CVE-2026-44839: RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.
1 issue left for the package maintainer to handle:
  • CVE-2025-30219: (needs triaging) RabbitMQ is a messaging and streaming broker. Versions prior to 4.0.3 are vulnerable to a sophisticated attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users. When a virtual host on a RabbitMQ node fails to start, recent versions will display an error message (a notification) in the management UI. The error message includes virtual host name, which was not escaped prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An attack that both makes a virtual host fail to start and creates a new virtual host name with an XSS code snippet or changes the name of an existing virtual host on disk could trigger arbitrary JavaScript code execution in the management UI (the user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ `4.0.3` and `3.13.8` patch the issue.

You can find information about how to handle this issue in the security team's documentation.

Created: 2025-03-26 Last update: 2026-05-29 22:33
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • CVE-2026-44839: RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.
Created: 2026-05-29 Last update: 2026-05-29 22:33
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2026-44839: RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.
Created: 2026-05-29 Last update: 2026-05-29 22:33
7 security issues in bullseye high

There are 7 open security issues in bullseye.

1 important issue:
  • CVE-2026-44839: RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.
6 issues postponed or untriaged:
  • CVE-2018-1279: (needs triaging) Pivotal RabbitMQ for PCF, all versions, uses a deterministically generated cookie that is shared between all machines when configured in a multi-tenant cluster. A remote attacker who can gain information about the network topology can guess this cookie and, if they have access to the right ports on any server in the MQ cluster can use this cookie to gain full control over the entire cluster.
  • CVE-2021-22116: (needs triaging) 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-32718: (needs triaging) RabbitMQ is a multi-protocol messaging broker. In rabbitmq-server prior to version 3.8.17, a new user being added via management UI could lead to the user's bane being rendered in a confirmation message without proper `<script>` tag sanitization, potentially allowing for JavaScript code execution in the context of the page. In order for this to occur, the user must be signed in and have elevated permissions (other user management). The vulnerability is patched in RabbitMQ 3.8.17. As a workaround, disable `rabbitmq_management` plugin and use CLI tools for management operations and Prometheus and Grafana for metrics and monitoring.
  • CVE-2021-32719: (needs triaging) RabbitMQ is a multi-protocol messaging broker. In rabbitmq-server prior to version 3.8.18, when a federation link was displayed in the RabbitMQ management UI via the `rabbitmq_federation_management` plugin, its consumer tag was rendered without proper <script> tag sanitization. This potentially allows for JavaScript code execution in the context of the page. The user must be signed in and have elevated permissions (manage federation upstreams and policies) for this to occur. The vulnerability is patched in RabbitMQ 3.8.18. As a workaround, disable the `rabbitmq_federation_management` plugin and use [CLI tools](https://www.rabbitmq.com/cli.html) instead.
  • CVE-2022-31008: (needs triaging) RabbitMQ is a multi-protocol messaging and streaming broker. In affected versions the shovel and federation plugins perform URI obfuscation in their worker (link) state. The encryption key used to encrypt the URI was seeded with a predictable secret. This means that in case of certain exceptions related to Shovel and Federation plugins, reasonably easily deobfuscatable data could appear in the node log. Patched versions correctly use a cluster-wide secret for that purpose. This issue has been addressed and Patched versions: `3.10.2`, `3.9.18`, `3.8.32` are available. Users unable to upgrade should disable the Shovel and Federation plugins.
  • CVE-2025-30219: (postponed; to be fixed through a stable update) RabbitMQ is a messaging and streaming broker. Versions prior to 4.0.3 are vulnerable to a sophisticated attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users. When a virtual host on a RabbitMQ node fails to start, recent versions will display an error message (a notification) in the management UI. The error message includes virtual host name, which was not escaped prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An attack that both makes a virtual host fail to start and creates a new virtual host name with an XSS code snippet or changes the name of an existing virtual host on disk could trigger arbitrary JavaScript code execution in the management UI (the user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ `4.0.3` and `3.13.8` patch the issue.
Created: 2026-05-29 Last update: 2026-05-29 22:33
lintian reports 5 errors and 34 warnings high
Lintian reports 5 errors and 34 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2026-03-04 Last update: 2026-05-20 15:01
The package has not entered testing even though the delay is over normal
The package has not entered testing even though the 5-day delay is over. Check why.
Created: 2026-05-25 Last update: 2026-06-04 00:32
1 open merge request in Salsa normal
There is 1 open merge request for this package on Salsa. You should consider reviewing and/or merging these merge requests.
Created: 2026-05-07 Last update: 2026-05-13 15:03
debian/patches: 2 patches to forward upstream low

Among the 2 debian patches available in version 4.3.0-2 of the package, we noticed the following issues:

  • 2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2023-02-26 Last update: 2026-05-19 19:01
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.6.2).
Created: 2022-05-11 Last update: 2026-05-19 18:00
testing migrations
  • excuses:
    • Migrates after: rabbitmqadmin-ng
    • Migration status for rabbitmq-server (4.0.5-14 to 4.3.0-2): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for rabbitmq-server/4.3.0-2: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for ruby-bunny/2.23.0-1: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), loong64: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
    • ∙ ∙ Reproducibility regression on amd64: rabbitmq-server
    • ∙ ∙ Reproducibility regression on arm64: rabbitmq-server
    • ∙ ∙ Reproducibility regression on armhf: rabbitmq-server
    • ∙ ∙ Reproducibility regression on i386: rabbitmq-server
    • ∙ ∙ Depends: rabbitmq-server rabbitmqadmin-ng (not considered)
    • Additional info (not blocking):
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/r/rabbitmq-server.html
    • ∙ ∙ 15 days old (needed 5 days)
    • Not considered
news
[rss feed]
  • [2026-05-19] Accepted rabbitmq-server 4.3.0-2 (source) into unstable (Thomas Goirand)
  • [2026-05-13] Accepted rabbitmq-server 4.3.0-1 (source all) into experimental (Thomas Goirand)
  • [2026-04-16] rabbitmq-server 4.0.5-14 MIGRATED to testing (Debian testing watch)
  • [2026-04-13] Accepted rabbitmq-server 4.0.5-14 (source) into unstable (Thomas Goirand)
  • [2026-03-06] rabbitmq-server 4.0.5-13 MIGRATED to testing (Debian testing watch)
  • [2026-03-03] Accepted rabbitmq-server 4.0.5-13 (source) into unstable (Thomas Goirand)
  • [2026-02-28] rabbitmq-server 4.0.5-12 MIGRATED to testing (Debian testing watch)
  • [2026-02-25] Accepted rabbitmq-server 4.0.5-12 (source) into unstable (Thomas Goirand)
  • [2026-02-24] rabbitmq-server 4.0.5-11 MIGRATED to testing (Debian testing watch)
  • [2026-02-16] Accepted rabbitmq-server 4.0.5-11 (source) into unstable (Thomas Goirand)
  • [2025-11-05] Accepted rabbitmq-server 4.0.5-6+deb13u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
  • [2025-08-25] rabbitmq-server 4.0.5-10 MIGRATED to testing (Debian testing watch)
  • [2025-08-21] Accepted rabbitmq-server 4.0.5-10 (source) into unstable (Thomas Goirand)
  • [2025-08-21] rabbitmq-server 4.0.5-9 MIGRATED to testing (Debian testing watch)
  • [2025-08-18] Accepted rabbitmq-server 4.0.5-9 (source) into unstable (Thomas Goirand)
  • [2025-08-17] rabbitmq-server 4.0.5-8 MIGRATED to testing (Debian testing watch)
  • [2025-08-15] Accepted rabbitmq-server 4.0.5-6+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Thomas Goirand)
  • [2025-08-11] Accepted rabbitmq-server 4.0.5-8 (source) into unstable (Thomas Goirand)
  • [2025-07-01] rabbitmq-server 4.0.5-6 MIGRATED to testing (Debian testing watch)
  • [2025-06-26] Accepted rabbitmq-server 4.0.5-6 (source) into unstable (Thomas Goirand)
  • [2025-06-03] rabbitmq-server 4.0.5-5 MIGRATED to testing (Debian testing watch)
  • [2025-05-27] Accepted rabbitmq-server 4.0.5-5 (source) into unstable (Thomas Goirand)
  • [2025-05-13] Accepted rabbitmq-server 4.0.5-4 (source) into unstable (Thomas Goirand)
  • [2025-03-16] rabbitmq-server 4.0.5-3 MIGRATED to testing (Debian testing watch)
  • [2025-03-10] Accepted rabbitmq-server 4.0.5-3 (source) into unstable (Thomas Goirand)
  • [2025-03-09] rabbitmq-server 4.0.5-2 MIGRATED to testing (Debian testing watch)
  • [2025-01-20] Accepted rabbitmq-server 4.0.5-2 (source) into unstable (Thomas Goirand)
  • [2024-12-17] Accepted rabbitmq-server 4.0.5-1 (source) into unstable (Thomas Goirand)
  • [2024-12-08] rabbitmq-server 3.10.8-4 MIGRATED to testing (Debian testing watch)
  • [2024-12-02] Accepted rabbitmq-server 3.10.8-4 (source) into unstable (Thomas Goirand)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian (5, 34)
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 4.0.5-10ubuntu5

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing