RabbitMQ rabbitmq-server
RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.2.0, < 4.2.6
- >= 4.1.0, < 4.1.11
- >= 4.0.0, < 4.0.21
- >= 3.13.0, < 3.13.15
Fixed in 4.2.6, 4.1.11, 4.0.21, 3.13.15
Mitigation
Upgrade rabbitmq-server to 4.2.6 or 4.1.11 or 4.0.21 or 3.13.15 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 39 days after publication; not in CISA KEV. First PoC: nuclei template: RabbitMQ Management - OAuth 2 Client Secret Disclosure (nuclei template, 19 Aug 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: RabbitMQ Management - OAuth 2 Client Secret Disclosure | 19 Aug 2026 | 14 Nov 2026 |