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.

CVSS 4.0

4.9CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

CVSS 3.1

6.5CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS

0.4% chance of exploitation in the next 30 days; higher than 28% of CVEs (scores of 2026-10-25)

CWE

CWE-863

Published

2026-07-10

Modified

2026-10-25

Record from

the NVD, synced 2026-10-25

Affected

• broadcom:rabbitmq_server

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

Check your stackJSON