CVE-2026-57219: RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations

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, the obsolete GET /api/auth endpoint can disclose the OAuth 2 client secret on RabbitMQ installations configured with management.oauthclientsecret, exposing credentials to unauthenticated callers when the management plugin and that OAuth configuration are enabled. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

Other sources

RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations

— Microsoft

Affected Software

3 affected componentsFixes available
RabbitMQ RabbitMQ<3.13.15, <4.0.20, <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
  6. Operational

    If you enabled RabbitMQ management with management.oauth_client_secret and the management plugin, rotate any OAuth 2 client secrets that may have been exposed to unauthenticated callers before applying the upgrade (fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6).

Event History

Jul 10, 2026
CVE Published
via MITRE·08:22 PM
Data Sourced
via MITRE·08:22 PM
DescriptionWeakness
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-57219?

CVE-2026-57219 has a high severity rating of 8.7 according to the CVSS scoring system.

2

How do I fix CVE-2026-57219?

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

3

What does CVE-2026-57219 affect?

CVE-2026-57219 affects RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

4

What kind of exposure does CVE-2026-57219 pose?

CVE-2026-57219 allows unauthenticated disclosure of OAuth 2 client credentials through an obsolete HTTP API endpoint.

5

How can I determine if my RabbitMQ installation is vulnerable to CVE-2026-57219?

You can determine vulnerability by checking if your RabbitMQ installation is running a version prior to the specified patched versions.

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