All vulnerabilities

Servers and applications

CVE-2026-57215

Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom

Severity
High 7.0
Published
24 Jun 2026
Last changed
25 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.13.15, 4.0.20, 4.1.11, 4.2.6
Exploit chance
0.4% in the next 30 daysHigher than 33% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
Attacker can
Read data
CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-5cq3-v9jx-p3x3
Sources
NVD, Project advisories (GitHub)

Description

RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to.* destinations due to a mismatch between volatile direct-reply-to queue handling and Khepri-backed binding deletion. Direct-reply-to queue names are treated as valid queue/target objects at bind and route time, but they are not persisted as queue records in Khepri. During unbind, binding deletion checks both endpoints through Khepri-backed lookup and can return ok without deleting the route entry when the volatile destination is missing from that store. The executed PoC showed this path in practice by delivering an injected message into a victim direct-reply-to consumer and then observing that the binding still existed after queue_unbind. The same run showed phantom routing behavior: mandatory return occurred for a truly empty exchange but not for the poisoned exchange.

An authenticated tenant with normal bind/publish permissions in a shared vhost can leave persistent poisoned routes that enable unsolicited reply-channel…

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 3.13.0 before 4.2.6
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 before 3.13.15
  • From 4.0.0 before 4.0.20
  • From 4.1.0 before 4.1.11
  • From 4.2.0 before 4.2.6

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-57215
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-57215
  • GitHub Advisory Database https://github.com/advisories/GHSA-5cq3-v9jx-p3x3
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-5cq3-v9jx-p3x3