CVE-2026-57219

nvd.nist.gov • July 15, 2026

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.

Denotes Vulnerable Software Are we missing a CPE here? Please let us know .

The full story

This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.

Critical RabbitMQ Vulnerabilities Enable Broker Takeover via OAuth Secrets Miggo Security discovered two critical vulnerabilities in RabbitMQ, a widely used open-source message broker. The flaws, CVE-2026-57219 and CVE-2026-57221, were present since early 2024 and allow unauthenticated attackers to access OAuth client secrets and authenticated users to enumerate queues and exchanges. CVE-2026-57219, with a CVSS score of 8.7, exposes the OAuth client secret through an obsolete management endpoint, enabling full broker takeover. CVE-2026-57221, with a CVSS score of 5.3, allows low-privileged users to view sensitive metadata. Both vulnerabilities affect RabbitMQ versions from 3.13.0 onward and have been patched in the latest releases. Organizations are advised to apply patches immediately and rotate any exposed OAuth secrets. 6 sources 73

Extracted Entities

CVE-2026-57219

The full story

Extracted Entities

Attack Types (1)

CVEs (1)

CWE Weaknesses (1)

Platforms (1)