CVE-2026-57218 RabbitMQ: AMQP 0-9-1 in combination with OAuth 2: consumer persistence can lead to post-revocation message disclosure

What is CVE-2026-57218?

CVE-2026-57218 is a medium-severity missing authorization vulnerability in Broadcom Rabbitmq Server, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-863

Which versions are affected by CVE-2026-57218?

It affects 1 product.

Products include Broadcom Rabbitmq Server.

How do I fix CVE-2026-57218?

Upgrade to a fixed version.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-57218 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57218 exists.

Other vulnerabilities in Broadcom Rabbitmq Server

• CVE-2016-9877 Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7 Critical 9.8
• CVE-2026-67404 RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch Critical 9.2
• CVE-2026-67231 RabbitMQ: Trust-store whitelist by Issuer+Serial only Critical 9.1
• CVE-2026-57219 Information disclosure in rabbitmq-server High 8.7
• CVE-2026-67236 RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login High 8.2

All Broadcom Rabbitmq Server vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as AZL-92346, DEBIAN-CVE-2026-57218, GHSA-wmrr-4h5v-5ch7, UBUNTU-CVE-2026-57218.