CVE-2026-57216
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, …
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/rabbitmq/rabbitmq-server/commit/7273c9eb6920abcde17b892dbe97ccaf906ead47
- github.com/rabbitmq/rabbitmq-server/commit/9f8c39fcf0acbc43080ee7017a62a02832114112
- github.com/rabbitmq/rabbitmq-server/pull/15936
- github.com/rabbitmq/rabbitmq-server/pull/15940
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-36m6-588r-vqcw
- nvd.nist.gov/vuln/detail/CVE-2026-57216
- cve.org/CVERecord?id=CVE-2026-57216
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.