CVE-2026-57216: RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks

Published Jul 10, 2026
·
Updated

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.

Other sources

RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks

— Microsoft

Affected Software

3 affected componentsFixes available
RabbitMQ RabbitMQ>0<3.13.15, >3.13.15<4.0.20, >4.0.20<4.1.11, >4.1.11<4.2.6
Broadcom Rabbitmq Server>=3.13.0<4.2.6
Microsoft azl3 rabbitmq-server 3.13.7-6<3.13.7-7
3.13.7-7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.13.7-7
  2. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 3.13.15
  3. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.0.20
  4. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.1.11
  5. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.2.6

Event History

Jul 10, 2026
CVE Published
via MITRE·08:20 PM
Data Sourced
via MITRE·08:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 15, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-57216?

CVE-2026-57216 is classified as critical with a severity score of 10.

2

How do I fix CVE-2026-57216?

To fix CVE-2026-57216, upgrade RabbitMQ to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6 or later.

3

What types of protocols are affected by CVE-2026-57216?

CVE-2026-57216 affects AMQP 0-9-1, AMQP 1.0, and Stream Protocol.

4

What can be exploited in CVE-2026-57216?

CVE-2026-57216 can be exploited to allow loopback-restricted users, such as guest, to connect remotely under certain conditions.

5

Which software versions are vulnerable to CVE-2026-57216?

RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6 are vulnerable to CVE-2026-57216.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203