rabbitmq-server: Insufficiently Protected Credentials
CVE-2026-57219 is a high-severity insufficiently protected credentials vulnerability in rabbitmq-server from Rabbitmq, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected rabbitmq-server versions: >= 4.2.0, < 4.2.6; >= 4.1.0, < 4.1.11; >= 4.0.0, < 4.0.21, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.84% chance of exploitation within 30 days, higher than 87% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of rabbitmq-server you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Rabbitmq | rabbitmq-server | >= 4.2.0, < 4.2.6; >= 4.1.0, < 4.1.11; >= 4.0.0, < 4.0.21; >= 3.13.0, < 3.13.15 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insufficiently Protected Credentials
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
How developers prevent this class of flaw
- Use an appropriate security mechanism to protect the credentials.
- Make appropriate use of cryptography to protect the credentials.
- Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
More Insufficiently Protected Credentials vulnerabilities (CWE-522)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- github.com/rabbitmq/rabbitmq-server/commit/98b1daf740237c85941e8addcbea6e74f4a2743c
- github.com/rabbitmq/rabbitmq-server/commit/aa387c4451e7b674df3e3ba89df86a99d697cc7f
- github.com/rabbitmq/rabbitmq-server/pull/16083Issue Tracking
- github.com/rabbitmq/rabbitmq-server/pull/16086Issue Tracking
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6Release Notes
Other vulnerabilities in rabbitmq-server
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 9.3 Critical severity
- 7.5 High severity
Recent Insufficiently Protected Credentials vulnerabilities
- 9.9 Critical severity
- 7.1 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 7.5 High severity
Spotted an error? Tell us.