CVE-2026-57219
HighPrior 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…
Published Jul 10, 2026 · Updated Sep 27, 2026 · Also known as DEBIAN-CVE-2026-57219, GHSA-pj24-8j6m-vq9q, UBUNTU-CVE-2026-57219
Key Facts
Patch in the next maintenance window- CVE-2026-57219 is a high-severity vulnerability (CVSS 8.7 v4) affecting Rabbitmq Server (Broadcom), Azl3 Rabbitmq-Server 3.13.7-6 (Microsoft), rabbitmq-server4 (redhat) and 5 more products.
- It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
- EPSS estimates a 2.8% probability of exploitation in the next 30 days.
- Fixed versions are available, including Rabbitmq Server 4.2.6, Rabbitmq Server 3.13.15, Rabbitmq Server 3.13.7-7.
- Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.
CVSS v4
8.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
EPSS (30-day exploit likelihood)
2.8%
Higher than 86.4% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
None known
Get the full CVE-2026-57219 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
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.
Affected Products
37 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Rabbitmq ServerBroadcom | >= >= 4.2.0, < 4.2.6 | 4.2.6 |
| Azl3 Rabbitmq-Server 3.13.7-6Microsoft | See advisory | n/a |
| rabbitmq-server4redhat | See advisory | 2-main-4.2.8-1.hum1 |
| erlang-rabbitmq-clientsuse | See advisory | 4.1.5-160000.2.1 |
| rabbitmq-server-bash-completionsuse | See advisory | 4.1.5-160000.2.1 |
Patched Releases
Rabbitmq Server
4.2.6, 3.13.15, 3.13.7-7, 4.0.20, 4.1.11, 4.1.5-160000.2.1, 4.3.0-2
erlang-rabbitmq-client
4.1.5-160000.2.1
rabbitmq-server-bash-completion
4.1.5-160000.2.1
rabbitmq-server-plugins
4.1.5-160000.2.1
rabbitmq-server-zsh-completion
4.1.5-160000.2.1
rabbitmq-server4
2-main-4.2.8-1.hum1
Timeline
Publicly disclosed
Jul 10, 2026
Last updated
Sep 27, 2026
Weakness Type
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- CWE-477 Use of Obsolete Function
- CWE-522 Insufficiently Protected Credentials
References
- advisoryRHSA-2026:35939
- advisoryRHSA-2026:35940
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2026/57xxx/CVE-2026-57219.json
- advisoryhttps://github.com/rabbitmq/rabbitmq-server/security/advisories
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-57219
FAQ
Common Questions.
RabbitMQ is a messaging and streaming broker.
Affected: Rabbitmq Server (Broadcom) versions >= >= 4.2.0, < 4.2.6; Azl3 Rabbitmq-Server 3.13.7-6 (Microsoft); rabbitmq-server4 (redhat), among others. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Rabbitmq Server 4.2.6, Rabbitmq Server 3.13.15, Rabbitmq Server 3.13.7-7.
Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.
Is CVE-2026-57219 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo