RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks
CVE-2026-57216 is fixed in rabbitmq-server on 1 platform, first by DEBIAN-CVE-2026-57216, released July 18, 2026. It is not reported as exploited. Patch Radar priority: High.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| rabbitmq-server · Debian 14 | 4.3.0-2 | DEBIAN-CVE-2026-57216 | Jul 18, 2026 |
| rabbitmq-server · opensuse-leap 16.0 | 4.1.5-160000.2.1 | OPENSUSE-SU-2026:21903-1 | Sep 22, 2026 |
| rabbitmq-server · sles 16.0 | 4.1.5-160000.2.1 | SUSE-SU-2026:23869-1 | Sep 22, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.