Unauthenticated OAuth client secret disclosure via obsolete endpoint
Published Jul 10, 2026 · Updated Jul 10, 2026
Information disclosure in affected RabbitMQ Server releases allows remote attackers to read an OAuth 2 client secret through the management HTTP API. The obsolete GET /api/auth route invokes rabbit_mgmt_wm_auth without an authorization check and serializes OAuth settings into its JSON response. Exposure requires the management plugin and management.oauth_client_secret configuration; successful requests disclose the configured credential.
Summary
What happened
Information disclosure in affected RabbitMQ Server releases allows remote attackers to read an OAuth 2 client secret through the management HTTP API. The obsolete GET /api/auth route invokes rabbit_mgmt_wm_auth without an authorization check and serializes OAuth settings into its JSON response. Exposure requires the management plugin and management.oauth_client_secret configuration; successful requests disclose the configured credential.
The record
- CVE
- CVE-2026-57219
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- RabbitMQ
- Product
- RabbitMQ Server
- Classifications
- CWE-200, CWE-522, T1552
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.13.0, < 3.13.15
- Affected versionversion=>= 4.0.0, < 4.0.21
- Affected versionversion=>= 4.1.0, < 4.1.11
- Affected versionversion=>= 4.2.0, < 4.2.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo