RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom
CVE-2026-57215 is fixed in rabbitmq-server on 1 platform, first by DEBIAN-CVE-2026-57215, 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, 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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| rabbitmq-server · Debian 14 | 4.3.0-2 | DEBIAN-CVE-2026-57215 | Jul 18, 2026 |
| rabbitmq-server · Fedora 43 | 4.0.9-5.fc43 | FEDORA-2026-548235EA3B | Jul 30, 2026 |
| rabbitmq-server · opensuse-leap 16.0 | 4.1.5-160000.3.1 | OPENSUSE-SU-2026:22163-1 | Nov 7, 2026 |
| rabbitmq-server · sles 16.0 | 4.1.5-160000.3.1 | SUSE-SU-2026:24442-1 | Nov 7, 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.