Description
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 products
broadcom: rabbitmq server
References7
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-36… ExploitVendor Advisory
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-36… ExploitVendor Advisory
- github.com/rabbitmq/rabbitmq-server/commit/7273c9eb6920abcde17b… Patch
- github.com/rabbitmq/rabbitmq-server/commit/9f8c39fcf0acbc43080e… Patch
- github.com/rabbitmq/rabbitmq-server/pull/15936 Issue TrackingPatch
- github.com/rabbitmq/rabbitmq-server/pull/15940 Issue TrackingPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6 Release Notes
Metrics
- CVSS 3.1
-
10.0
CRITICAL
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 44 · as of 15 November 2026
- CWE
- CWE-287
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.