CVE-2026-57216
published 2026-07-10CVE-2026-57216: 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…
PriorityP264critical10CVSS 3.1
AVNACLPRNUINSCCHIHAH
EPSS
0.50%
42.2th percentile
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.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| broadcom | rabbitmq_server | >= 3.13.0 < 3.13.15 | 3.13.15 |
| broadcom | rabbitmq_server | >= 4.0.0 < 4.0.20 | 4.0.20 |
| broadcom | rabbitmq_server | >= 4.1.0 < 4.1.11 | 4.1.11 |
| broadcom | rabbitmq_server | >= 4.2.0 < 4.2.6 | 4.2.6 |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
| rabbitmq | rabbitmq-server | — | — |
CVSS provenance
nvdv3.110.0CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
vendor_redhat10.0CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
rabbitmq: RabbitMQ: Authentication bypass allows remote connection for loopback-restricted users via incorrect loopback check
vendor_redhat·2026-07-10·CVSS 10.0
CVE-2026-57216 [CRITICAL] CWE-358 rabbitmq: RabbitMQ: Authentication bypass allows remote connection for loopback-restricted users via incorrect loopback check
rabbitmq: RabbitMQ: Authentication bypass allows remote connection for loopback-restricted users via incorrect loopback check
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.
A flaw was found in RabbitMQ, a messaging and streaming broker. The AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication mechanisms incorrectly perform a loopback check. This
VulDB
RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5 Authentication infinite loop
vuldb·2026-07-10·CVSS 6.8
CVE-2026-57216 [MEDIUM] RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5 Authentication infinite loop
A vulnerability was found in RabbitMQ up to 3.13.14/4.0.19/4.1.10/4.2.5. It has been declared as problematic. This impacts an unknown function of the component Authentication Handler. The manipulation results in infinite loop.
This vulnerability was named CVE-2026-57216. The attack may be performed from remote. There is no available exploit.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/rabbitmq/rabbitmq-server/commit/7273c9eb6920abcde17b892dbe97ccaf906ead47https://github.com/rabbitmq/rabbitmq-server/commit/9f8c39fcf0acbc43080ee7017a62a02832114112https://github.com/rabbitmq/rabbitmq-server/pull/15936https://github.com/rabbitmq/rabbitmq-server/pull/15940https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-36m6-588r-vqcwhttps://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-36m6-588r-vqcw
2026-07-10
Published