RabbitMQ Flaw Can Expose OAuth Secrets; Updates Fix Queue-Enumeration Bug

· Original article ↗

Summary

CVE-2026-57219 can expose RabbitMQ’s OAuth secret through an unauthenticated management endpoint in affected configurations. Updates also fix CVE-2026-57221, which lets authenticated users enumerate queues and exchanges. No in-the-wild exploitation is known.

Key points

  • CVE-2026-57219 (CVSS 8.7) affects RabbitMQ’s obsolete management endpoint, which can return the OAuth secret without authentication when a client secret is configured.
  • An attacker able to reach the management port could use the exposed secret to impersonate the broker and obtain an administrator token, according to Miggo.
  • Deployments without a configured client secret or without the management plugin are not affected by CVE-2026-57219.
  • CVE-2026-57221 (CVSS 5.3) allows any authenticated user to enumerate queues and exchanges and read their statistics.
  • Fixed versions are 4.3.0, 4.2.6, 4.1.11, 4.0.20, and 3.13.15; CVE-2026-57219 was introduced in version 3.13.0.
  • Miggo says there is no evidence of in-the-wild exploitation. Recommended steps include updating, restricting management-port access, segmenting networks, and rotating the OAuth client secret.

Article Details

Vulnerability Types
  • Unauthenticated disclosure of the OAuth client secret
  • Missing authorization allowing authenticated users to enumerate queues and exchanges and read their statistics
Severity
CVE-2026-57219: CVSS 8.7; CVE-2026-57221: CVSS 5.3
Affected Versions
  • RabbitMQ 3.13.0 (the version in which CVE-2026-57219 was introduced)
Exploitation Status
not_reported
Exploit Availability
unknown
Patch Status
available
Workarounds
  • If patching is not possible, block access to vulnerable instances.
  • Ensure the management interface is not exposed to the internet and implement network segmentation.
  • Rotate the OAuth client secret.

MITRE ATT&CK

CVE

Products

Related Articles