Auth bypass in Broadcom Rabbitmq Server
CVE-2026-57218
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled or reauthorized at delivery time after the channel user state changes. This issue is fixed in version 4.2.6.
Vulnerability class: Broken Access Control
EPSS: 0.006 (44.4th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N.
Affected products
- Broadcom Rabbitmq_server
- Rabbitmq Rabbitmq-server — versions >= 4.2.0, < 4.2.6
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
- security-advisories@github.com (Patch, x_refsource_MISC, Issue Tracking)
- security-advisories@github.com (Patch, x_refsource_MISC, Issue Tracking)
- security-advisories@github.com (Patch, x_refsource_MISC)
- security-advisories@github.com (Patch, x_refsource_MISC)
- security-advisories@github.com (x_refsource_MISC, Release Notes)
Frequently asked questions
- What is CVE-2026-57218?
- CVE-2026-57218 is a medium-severity vulnerability in Broadcom Rabbitmq Server, classified under Incorrect Authorization. CVSS score: 6.5/10. Published 2026-07-10.
- How severe is CVE-2026-57218?
- Medium severity. CVSS v3 base score is 6.5 out of 10.