# CVE-2026-57215: 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.

- Web page: https://patchblox.com/security/cve/CVE-2026-57215
- Priority: High
- CVSS: 8.8 (Important)
- EPSS: 0.0038
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jul 10, 2026
- Weakness: Incorrect Authorization
- Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-57215

## Description

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

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | rabbitmq-server Debian 14 | 4.3.0-2 | [DEBIAN-CVE-2026-57215](https://patchblox.com/security/data/fix/linux/debian-cve-2026-57215.md) | Jul 18, 2026 |
| Linux | rabbitmq-server Fedora 43 | 4.0.9-5.fc43 | [FEDORA-2026-548235EA3B](https://patchblox.com/security/data/fix/linux/fedora-2026-548235ea3b.md) | Jul 30, 2026 |
| Linux | rabbitmq-server opensuse-leap 16.0 | 4.1.5-160000.3.1 | [OPENSUSE-SU-2026:22163-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2026-22163-1.md) | Nov 7, 2026 |
| Linux | rabbitmq-server sles 16.0 | 4.1.5-160000.3.1 | [SUSE-SU-2026:24442-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-24442-1.md) | Nov 7, 2026 |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

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.