CVE-2026-57219

Analyzed Analyzed - Analysis Complete

OAuth 2 Client Secret Disclosure in RabbitMQ

Publication date: 2026-07-10

Last updated on: 2026-07-29

Assigner: GitHub, Inc.

Description

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.oauth_client_secret, 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-10

Last Modified

2026-07-29

Generated

2026-07-31

AI Q&A

2026-07-11

EPSS Evaluated

2026-07-28

NVD

CVE-2026-57219

Affected Vendors & Products

Vendor	Product	Version / Range
broadcom	rabbitmq_server	From 3.13.0 (inc) to 4.2.6 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-200	The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-522	The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

Attack-Flow Graph

Executive Summary

This vulnerability exists in RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6. It involves an obsolete API endpoint, GET /api/auth, which can disclose the OAuth 2 client secret if RabbitMQ is configured with management.oauth_client_secret and the management plugin is enabled. This means that unauthenticated attackers can access sensitive OAuth 2 client credentials through this endpoint.

Impact Analysis

The impact of this vulnerability is the exposure of OAuth 2 client secrets to unauthenticated users. This can lead to unauthorized access to systems or services that rely on these credentials for authentication, potentially allowing attackers to impersonate legitimate clients, access sensitive data, or disrupt messaging and streaming operations managed by RabbitMQ.

Compliance Impact

This vulnerability can lead to the disclosure of OAuth 2 client secrets to unauthenticated callers, which may result in unauthorized access to sensitive data or systems.

Such unauthorized disclosure of credentials could potentially violate data protection and privacy regulations like GDPR and HIPAA, which require strict controls over access to sensitive information.

Therefore, organizations using affected RabbitMQ versions without the fix might face compliance risks if this vulnerability is exploited.

Mitigation Strategies

To mitigate this vulnerability, upgrade RabbitMQ to one of the fixed versions: 3.13.15, 4.0.20, 4.1.11, or 4.2.6.

Ensure that the management plugin and the management.oauth_client_secret configuration are properly secured or disabled if not needed, as the vulnerability exposes OAuth 2 client secrets via the obsolete GET /api/auth endpoint.

Hi! I’m here to help you understand CVE-2026-57219. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70