Vulnerability Details 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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.003
EPSS Ranking 18.6%
CVSS Severity
CVSS v3 Score 6.5
References
- https://github.com/rabbitmq/rabbitmq-server/commit/501ad947cd6bbcc9486fe96e0d073992bfe52cc4
- https://github.com/rabbitmq/rabbitmq-server/commit/db20d6c0fcf3056030f244b5adab0d45c0db0c9e
- https://github.com/rabbitmq/rabbitmq-server/pull/16092
- https://github.com/rabbitmq/rabbitmq-server/pull/16097
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-wmrr-4h5v-5ch7
- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-wmrr-4h5v-5ch7
Products affected by CVE-2026-57218
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.0
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.1
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.2
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.3
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.4
-
cpe:2.3:a:broadcom:rabbitmq_server:4.2.5