Description
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ does not perform authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations, allowing any authenticated user who can connect to a virtual host to enumerate queue and exchange names and read queue message and consumer counts. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Published: 2026-07-10
Score: 5.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The flaw allows any authenticated user who can connect to a virtual host in RabbitMQ Server to perform passive queue.declare and exchange.declare operations without the server verifying permissions. This bypass lets the user enumerate existing queue and exchange names and read message and consumer counts, thereby leaking metadata about the messaging environment. This users to gain data they are not permitted to access.

Affected Systems

RabbitMQ Server is affected. Any installation running a version prior to 3.13.15, 4.0.20, 4.1.11, or 4.2.6 is vulnerable. The issue is announced for rabbitmq:rabbitmq-server.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. The EPSS score is below 1%, showing a low likelihood of exploitation, and the vulnerability is not listed in the CISA KEV catalog. An attacker needs to be authenticated to a virtual host; once authenticated, they can enumerate queue and exchange names and read message and consumer counts via passive declare operations, without requiring privilege escalation or code execution.

Generated by OpenCVE AI on July 28, 2026 at 08:10 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade RabbitMQ Server to version 3.13.15, 4.0.20, 4.1.11, 4.2.6, or later.
  • Restrict virtual host access by configuring permissions to limit which authenticated users can perform declare operations and removing unnecessary user accounts.
  • Apply network segmentation or firewall rules to restrict external access to the RabbitMQ broker port, ensuring only trusted hosts can connect.

Generated by OpenCVE AI on July 28, 2026 at 08:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 28 Jul 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-425
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.0, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N'}

threat_severity

Moderate


Mon, 13 Jul 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 10 Jul 2026 22:30:00 +0000

Type Values Removed Values Added
First Time appeared Rabbitmq
Rabbitmq rabbitmq-server
Vendors & Products Rabbitmq
Rabbitmq rabbitmq-server

Fri, 10 Jul 2026 20:45:00 +0000

Type Values Removed Values Added
Description RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ does not perform authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations, allowing any authenticated user who can connect to a virtual host to enumerate queue and exchange names and read queue message and consumer counts. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Title RabbitMQ: Passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to unprivileged users
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N'}


Subscriptions

Rabbitmq Rabbitmq-server
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-13T18:05:48.847Z

Reserved: 2026-06-24T02:21:33.810Z

Link: CVE-2026-57221

cve-icon Vulnrichment

Updated: 2026-07-13T18:05:00.820Z

cve-icon NVD

No data.

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-07-10T20:24:27Z

Links: CVE-2026-57221 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-07-28T08:15:06Z

Weaknesses
  • CWE-425

    Direct Request ('Forced Browsing')

  • CWE-862

    Missing Authorization