CVE-2026-57215: RabbitMQ incorrect authorization in amq.rabbitmq.reply-to bindings

CVE-2026-57215 · Severity: info · CVSS 7 · Published 2026-07-10

RabbitMQ is a widely used message broker that facilitates communication between different software applications. A vulnerability in certain versions allows unauthorized users to create persistent message routing entries to internal 'reply-to' destinations that should be temporary. This could allow an attacker to intercept or redirect private application responses, potentially leading to the exposure of sensitive data or disruption of service operations.

Technologies: Broadcom Rabbitmq Server. Vendors: Broadcom.

Quick answers

Is CVE-2026-57215 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-57215 being exploited in the wild.
How severe is CVE-2026-57215?
Informational severity, with a CVSS score of 7, published 10 July 2026.
Which products and versions are affected?
Broadcom Rabbitmq Server >= 3.13.0, < 3.13.15; >= 4.0.0, < 4.0.21; >= 4.1.0, < 4.1.11; >= 4.2.0, < 4.2.6.
Is there a fix for CVE-2026-57215?
A patch was published on 2026-04-05: Initial fix committed to main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57215 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-57215?
Check whether you run Broadcom Rabbitmq Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

RabbitMQ is vulnerable to an incorrect authorization flaw (CWE-863) where it allows foreign bindings to 'amq.rabbitmq.reply-to' destinations. The root cause is that volatile direct-reply-to queues are accepted at bind and route time but are omitted from Khepri-backed deletion checks. This results in persistent route entries remaining in the system even after an unbind operation. An attacker with low-privileged network access can exploit this to establish unauthorized bindings, potentially intercepting messages intended for other clients. The issue is fixed in RabbitMQ versions 3.13.15, 4.0.21, 4.1.11, and 4.2.6.

Affected products

  • RabbitMQ RabbitMQ Server >= 3.13.0, < 3.13.15; >= 4.0.0, < 4.0.21; >= 4.1.0, < 4.1.11; >= 4.2.0, < 4.2.6

Timeline

  • 2026-04-05: patched: Initial fix committed to main branch
  • 2026-07-10: disclosed: CVE published and advisory released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.