UBUNTU-CVE-2026-57216
RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6 contain a vulnerability in the AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication mechanisms. This flaw allows a loopback-restricted user such as 'guest' to connect remotely if traffic is accepted through a trusted PROXY-protocol path and the backend listener is bound to loopback. The issue arises because the loopback check uses the listener-side socket address instead of the actual client source address. Fixed versions include 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
AI Analysis
Technical Summary
RabbitMQ before versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6 has an authentication bypass vulnerability affecting AMQP 0-9-1, AMQP 1.0, and Stream Protocols. The vulnerability allows a user restricted to loopback access (e.g., the 'guest' user) to connect remotely when traffic is routed through a trusted PROXY-protocol path. This occurs because the loopback verification incorrectly uses the listener-side socket address rather than the true client source address, enabling unauthorized remote connections. The issue is resolved in the specified fixed versions.
Potential Impact
An attacker with a loopback-restricted user account (such as 'guest') can bypass the loopback restriction and connect remotely to the RabbitMQ broker if the traffic passes through a trusted PROXY-protocol path. This could lead to unauthorized access to the messaging broker with potentially high confidentiality impact, as indicated by the CVSS vector (confidentiality high, integrity none, availability none). No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to one of these versions or later to remediate the vulnerability. No other vendor advisory or patch links were provided; therefore, check the official RabbitMQ or Ubuntu security advisories for the latest updates and patches.
UBUNTU-CVE-2026-57216
Description
RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6 contain a vulnerability in the AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication mechanisms. This flaw allows a loopback-restricted user such as 'guest' to connect remotely if traffic is accepted through a trusted PROXY-protocol path and the backend listener is bound to loopback. The issue arises because the loopback check uses the listener-side socket address instead of the actual client source address. Fixed versions include 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
CVSS v3.1
Score 6.8medium
Affected software
pkg:deb/ubuntu/[email protected]+esm2?arch=source&distro=esm-infra/xenialpkg:deb/ubuntu/[email protected]?arch=source&distro=bionicpkg:deb/ubuntu/[email protected]?arch=source&distro=focalpkg:deb/ubuntu/[email protected]?arch=source&distro=jammypkg:deb/ubuntu/[email protected]?arch=source&distro=noblepkg:deb/ubuntu/[email protected]?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ before versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6 has an authentication bypass vulnerability affecting AMQP 0-9-1, AMQP 1.0, and Stream Protocols. The vulnerability allows a user restricted to loopback access (e.g., the 'guest' user) to connect remotely when traffic is routed through a trusted PROXY-protocol path. This occurs because the loopback verification incorrectly uses the listener-side socket address rather than the true client source address, enabling unauthorized remote connections. The issue is resolved in the specified fixed versions.
Potential Impact
An attacker with a loopback-restricted user account (such as 'guest') can bypass the loopback restriction and connect remotely to the RabbitMQ broker if the traffic passes through a trusted PROXY-protocol path. This could lead to unauthorized access to the messaging broker with potentially high confidentiality impact, as indicated by the CVSS vector (confidentiality high, integrity none, availability none). No known exploits in the wild have been reported.
Mitigation Recommendations
A fix is available in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to one of these versions or later to remediate the vulnerability. No other vendor advisory or patch links were provided; therefore, check the official RabbitMQ or Ubuntu security advisories for the latest updates and patches.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-57216
- Osv Schema Version
- 1.7.0
- Aliases
- []
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:18.04:LTS","Ubuntu:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.04:LTS"]
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a58b46968715ace43d79842
Added to database: 07/16/2026, 10:37:29 UTC
Last enriched: 07/16/2026, 11:41:34 UTC
Last updated: 07/31/2026, 19:24:48 UTC
Views: 4
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.