CVE-2026-57215: RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom
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.
Other sources
RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 3.13.7-7 - Upgrade
Upgrade
RabbitMQto a version that resolves this vulnerability.Fixed in 3.13.15 - Upgrade
Upgrade
RabbitMQto a version that resolves this vulnerability.Fixed in 4.0.20 - Upgrade
Upgrade
RabbitMQto a version that resolves this vulnerability.Fixed in 4.1.11 - Upgrade
Upgrade
RabbitMQto a version that resolves this vulnerability.Fixed in 4.2.6
Event History
Frequently Asked Questions
What is the severity of CVE-2026-57215?
The severity of CVE-2026-57215 is high with a score of 7.
How do I fix CVE-2026-57215?
To fix CVE-2026-57215, upgrade RabbitMQ to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later.
What are the potential risks associated with CVE-2026-57215?
The potential risks associated with CVE-2026-57215 include unauthorized reply-channel injection and persistent phantom issues.
Which versions of RabbitMQ are affected by CVE-2026-57215?
RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6 are affected by CVE-2026-57215.
What is the impact of CVE-2026-57215 on RabbitMQ users?
The impact of CVE-2026-57215 allows malicious actors to create unauthorized bindings, compromising the integrity of the messaging system.