RabbitMQ Security
As the steward of RabbitMQ, we at Broadcom take the security of RabbitMQ very seriously.
How to Report a Vulnerability
To responsibly disclose a vulnerability:
- Navigate to the
Security and qualitytab of the relevant repository on GitHub. For example:rabbitmq/rabbitmq-serverfor the core brokerrabbitmq/rabbitmq-amqp-java-clientfor the RabbitMQ AMQP 1.0 Java clientrabbitmq/cluster-operatorfor the RabbitMQ Kubernetes cluster operator
- Click
Report a vulnerabilityto open a private advisory draft. - Provide details, including steps to reproduce.
If you are unable to use GitHub Security Advisories, you can email tnz-rabbitmq-core.pdl@broadcom.com.
Our team will review the report, triage it, and work with you to resolve the issue privately before issuing a public patch and advisory.
Please do not report security vulnerabilities via public GitHub issues, public mailing lists, or public Discord channels.
Security Advisories
For commercial Broadcom / VMware Tanzu Customers
If you are a commercial customer using VMware Tanzu RabbitMQ or other commercial distributions, please refer to the Broadcom Security Advisories.
The Broadcom Support Portal is the authoritative source of truth for all commercial releases. It includes comprehensive vulnerability information, including CVEs in dependencies and underlying Erlang runtime that are not listed on this page.
You can search the Broadcom Security Advisories for a specific RabbitMQ version. For example, if you type RabbitMQ 4.2.8 into the search box, you will see the security advisory for that specific release.
Open Source Advisories
For convenience, the table below lists all public security advisories across the RabbitMQ GitHub organization.
| Advisory ID & CVE ID | Date Published 🔽 | Severity | Repository | Summary | Affected Versions | Patched Versions |
|---|---|---|---|---|---|---|
CVE ID pending | 2026-10-25 | Medium | rabbitmq-server | SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` output | >= 4.3.0, < 4.3.7>= 4.2.0, < 4.2.12>= 4.1.0, < 4.1.17>= 3.13.0, < 3.13.21 | |
CVE ID pending | 2026-10-25 | Medium | rabbitmq-server | AMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumers | >= 4.3.0, < 4.3.7>= 4.2.0, < 4.2.12>= 4.1.0, < 4.1.17 | |
CVE ID pending | 2026-10-25 | High | rabbitmq-server | Memory DoS via incomplete AMQP 0-9-1 messages | >= 4.3.0, < 4.3.7>= 4.2.0, < 4.2.12>= 4.1.0, < 4.1.17>= 3.13.0, < 3.13.21 | |
CVE ID pending | 2026-10-25 | Medium | rabbitmq-server | HTML injection in management UI OAuth login warning | >= 4.3.0, < 4.3.7>= 4.2.0, < 4.2.12>= 4.1.0, < 4.1.17>= 3.13.0, < 3.13.21 | |
CVE ID pending | 2026-10-25 | High | rabbitmq-server | LDAP authentication failures allow unauthenticated log amplification | >= 4.3.0, < 4.3.7>= 4.2.0, < 4.2.12>= 4.1.0, < 4.1.17>= 3.13.0, < 3.13.21 | |
| 2026-10-01 | Medium | rabbitmq-java-client | JSONReader in the default JSON-RPC mapper never terminates on truncated input, causing DoS | <= 5.36.0 | 5.37.0 | |
CVE ID pending | 2026-09-18 | Medium | rabbitmq-server | RabbitMQ STOMP consumers retain OAuth queue access after JWT expiration | >= 4.3.0, < 4.3.6>= 4.2.0, < 4.2.11 | |
CVE ID pending | 2026-09-18 | Low | rabbitmq-server | RabbitMQ Stream Publisher Management API Discloses Unauthorized Vhost and Stream Existence | >= 4.3.0, < 4.3.6>= 4.2.0, < 4.2.11 | |
CVE ID pending | 2026-09-18 | Medium | rabbitmq-server | MQTT retained message store has no size or count limit and is never reclaimed | >= 4.3.0, < 4.3.5 | |
CVE ID pending | 2026-09-18 | Low | rabbitmq-server | Cross-vhost Stream consumer virtual-host existence disclosure | >= 4.3.0, < 4.3.6>= 4.2.0, < 4.2.11 |