CVE-2026-57216: CWE-287: Improper Authentication in rabbitmq rabbitmq-server
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.
AI Analysis
Technical Summary
RabbitMQ server versions before 3.13.15, 4.0.20, 4.1.11, and 4.2.6 have an improper authentication vulnerability (CWE-287) in AMQP 0-9-1, AMQP 1.0, and Stream Protocols. The vulnerability arises because the loopback check uses the listener-side socket address instead of the actual client source address when traffic is routed through a trusted PROXY-protocol path. This allows a user restricted to loopback access, such as the 'guest' user, to connect remotely, bypassing intended access controls. The issue is resolved in the fixed versions.
Potential Impact
An attacker can bypass loopback restrictions and authenticate remotely as a loopback-restricted user (e.g., 'guest') when the server accepts traffic via a trusted PROXY-protocol path. This leads to unauthorized access with high confidentiality impact but no integrity or availability impact. The CVSS score is 6.8 (medium severity).
Mitigation Recommendations
Upgrade rabbitmq-server to version 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory stating these versions contain the fix. No other mitigation is specified.
CVE-2026-57216: CWE-287: Improper Authentication in rabbitmq rabbitmq-server
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.
CVSS v3.1
Score 6.8medium
Affected software
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ server versions before 3.13.15, 4.0.20, 4.1.11, and 4.2.6 have an improper authentication vulnerability (CWE-287) in AMQP 0-9-1, AMQP 1.0, and Stream Protocols. The vulnerability arises because the loopback check uses the listener-side socket address instead of the actual client source address when traffic is routed through a trusted PROXY-protocol path. This allows a user restricted to loopback access, such as the 'guest' user, to connect remotely, bypassing intended access controls. The issue is resolved in the fixed versions.
Potential Impact
An attacker can bypass loopback restrictions and authenticate remotely as a loopback-restricted user (e.g., 'guest') when the server accepts traffic via a trusted PROXY-protocol path. This leads to unauthorized access with high confidentiality impact but no integrity or availability impact. The CVSS score is 6.8 (medium severity).
Mitigation Recommendations
Upgrade rabbitmq-server to version 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor advisory stating these versions contain the fix. No other mitigation is specified.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-24T02:21:33.810Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a515a8b68715ace432d830a
Added to database: 07/10/2026, 20:48:11 UTC
Last enriched: 07/18/2026, 15:45:23 UTC
Last updated: 08/24/2026, 10:52:10 UTC
Views: 140
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.