rabbitmq-server: Improper Authentication
CVE-2026-57216 is a critical-severity improper authentication vulnerability in rabbitmq-server from Rabbitmq, with a CVSS 3.1 base score of 10.0 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 0.5% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
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
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 6.8 | Medium | CNA (github.com) |
| CVSS 3.1 | 10.0 | Critical | 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, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. 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: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/rabbitmq/rabbitmq-server/commit/7273c9eb6920abcde17b892dbe97ccaf906ead47
- github.com/rabbitmq/rabbitmq-server/commit/9f8c39fcf0acbc43080ee7017a62a02832114112
- github.com/rabbitmq/rabbitmq-server/pull/15936Issue Tracking
- github.com/rabbitmq/rabbitmq-server/pull/15940Issue 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 Improper Authentication vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 9.6 Critical severity
- 7.4 High severity
- 8.3 High severity
- 8.1 High severity
Spotted an error? Tell us.