CVE-2026-57218
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/rabbitmq/rabbitmq-server/commit/501ad947cd6bbcc9486fe96e0d073992bfe52cc4
- github.com/rabbitmq/rabbitmq-server/commit/db20d6c0fcf3056030f244b5adab0d45c0db0c9e
- github.com/rabbitmq/rabbitmq-server/pull/16092
- github.com/rabbitmq/rabbitmq-server/pull/16097
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-wmrr-4h5v-5ch7
- nvd.nist.gov/vuln/detail/CVE-2026-57218
- cve.org/CVERecord?id=CVE-2026-57218
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.