RabbitMQ Go Stream client 1.5.8 is a newbug fix release that includes a critical fix.

The fix reverts the pull request 393 that introduced a dangerous bug where the library skipped chunk delivery when the channel's maximum capacity was reached. In practical terms, message dispatch to the application would stop.

The bug was triggered when the consumer was experiencing a near peak delivery pressure for some time, or when the consumer was consistently slow to process the deliveries.

Affected versions​

The bug affects the following versions: 1.5.5, 1.5.6 and 1.5.7.

We strongly recommend updating the client to 1.5.8 as soon as possible.

RabbitMQ is not affected by CVE-2025-32433, a vulnerability in the Erlang's SSH library. RabbitMQ does not use SSH, neither the server nor the client parts.

We are delighted to announce support for AMQP 1.0 over WebSocket in VMware Tanzu RabbitMQ 4.1.

This feature enables any browser-based application to communicate with RabbitMQ using AMQP 1.0, paving the way for a wide range of efficient browser-based business messaging scenarios.

RabbitMQ 4.1.0 is a new minor release that includes multiple performance improvements, and a number of features such as thew new peer discovery mechanism for Kubernetes.

See Compatibility Notes below to learn about breaking or potentially breaking changes in this release.

RabbitMQ 4.0.9 is a new patch release in the 4.0.x series.

Release Artifacts​

Release artifacts can be obtained on GitHub as well as RPM, Debian package repositories.

Community Support Now Only Covers the 4.1.x Series​

With the release of RabbitMQ 4.1.0, this series is no longer covered by community support.

Future 4.0.x releases will only be available to paying customers via the Broadcom customer portal.

All non-paying users must upgrade to 4.1.0 in order to be covered by community support from the core team.

Upgrade Guidance​

If upgrading from a version prior to 4.0, please consult the 4.0 release notes.

RabbitMQ 4.1 is around the corner (update: has been released) and, as usual, apart from new features, we have made some internal changes that should provide better performance.

There are at least 4 notable changes:

1. Lower and more stable memory usage for quorum queues
2. Much better performance when consuming a long quorum queue
3. Better performance for Websocket connections
4. Lower memory usage and/or higher throughput for TCP connections

RabbitMQ 4.1 includes a completely redesigned peer discovery plugin for Kubernetes. No configuration changes should be needed when upgrading to 4.1, so if you want, you can just stop reading here. If you are interested in the details, read on. This blog post explains the peer discovery subsystem in general and the changes to rabbitmq_peer_discovery_k8s in particular.

RabbitMQ 4.0.7​

RabbitMQ 4.0.7 is a new patch release in the 4.0.x series.

This series is currently covered by community support.

Release Artifacts​

Release artifacts can be obtained on GitHub as well as RPM, Debian package repositories.

Upgrade Guidance​

If upgrading from a version prior to 4.0, please consult the 4.0 release notes.

RabbitMQ 4.0.6​

RabbitMQ 4.0.6 is a new patch release in the 4.0.x series.

This series is currently covered by community support.

Release Artifacts​

Release artifacts can be obtained on GitHub as well as RPM, Debian package repositories.

Upgrade Guidance​

If upgrading from a version prior to 4.0, please consult the 4.0 release notes.

RabbitMQ 3.13.8 is a new patch release in the 3.13.x series. This series is currently covered by commercial support only.

For publicly available open source releases, see the 4.0.x series.

Release Artifacts

Release artifacts for the 3.13.x series can be obtained via the Broadcom customer portal.

Upgrade Guidance

If upgrading from a version prior to 3.13.9, please consult the 3.13.0 release notes.