CVE-2026-57219 rabbitmq CVE debrief

Who should care

Users of RabbitMQ, especially those with management plugin and OAuth configuration enabled, should be aware of this vulnerability and take steps to mitigate it. This includes reviewing and updating OAuth configurations to minimize exposure and disabling the management plugin if not in use.

Technical summary

The vulnerability exists in the obsolete GET /api/auth endpoint of RabbitMQ. When the management plugin and OAuth configuration are enabled, this endpoint can disclose the OAuth 2 client secret to unauthenticated callers. The issue arises from the endpoint's ability to expose credentials. The vulnerability has a CVSS score of 8.7 and is classified as HIGH. RabbitMQ installations that have the management plugin and OAuth configuration enabled should be patched to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6.

Defensive priority

High priority should be given to patching RabbitMQ installations that have the management plugin and OAuth configuration enabled.

Recommended defensive actions

• Patch RabbitMQ installations to versions 3.13.15, 4.0.20, 4.1.11, or 4.2.6.
• Disable the management plugin if not in use.
• Review and update OAuth configurations to minimize exposure.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD detail provide information on the vulnerability. Additional details can be found in the source references provided. The RabbitMQ management plugin and OAuth configuration must be verified for exposure. Defenders should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance.

Official resources