RabbitMQ Passive Declaration Authorization Bypass
CVE-2026-57221 is a missing-authorization vulnerability in RabbitMQ's AMQP 0-9-1 passive queue.declare and exchange.declare operations. Affected implementations omit resource permission checks, allowing an authenticated user who can connect to a virtual host to probe known or guessed queue and exchange names and obtain queue message and consumer counts, regardless of resource permissions. The vulnerability exposes messaging infrastructure metadata but does not permit reading or modifying message contents. Fixed releases include RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Authenticated users can discover queues and exchanges and retrieve queue message and consumer counts within virtual hosts they can access. This weakens isolation between applications or tenants sharing a virtual host, allowing unauthorized mapping of messaging topology, inference of workload or business activity, and reconnaissance for subsequent attacks. The vulnerability does not itself expose message contents, permit message tampering, or cause a demonstrated availability impact.
If you can’t patch tonight, do this now.
No configuration workaround or WAF rule corrects the missing authorization checks. Until patching is possible, separate tenants into distinct virtual hosts and restrict each account's virtual-host connectivity to its intended tenant. Restrict AMQP listener access to trusted clients and networks to reduce exposure. Resource-level permissions alone do not prevent exploitation on affected releases.
Patch, then assume compromise.
Upgrade to RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.0, or a later vendor-supported release containing the fix, as appropriate for the deployed branch. Update affected distribution packages, pinned container images, Helm deployments, and products embedding RabbitMQ. The fix enforces authorization on passive queue and exchange declarations through check_configure_permitted.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.