Authorization Bypass Through User-Controlled Key Affecting rabbitmq-server4.3 package, versions <0:4.3.6-1.hum1


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.26% (17th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-RABBITMQSERVER43-20132552
  • published25 Sept 2026
  • disclosed23 Sept 2026

Introduced: 23 Sep 2026

CVE-2026-66076  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

Upgrade RHEL:10 rabbitmq-server4.3 to version 0:4.3.6-1.hum1 or higher.
This issue was patched in RHSA-2026:67552.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rabbitmq-server4.3 package and not the rabbitmq-server4.3 package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, is_authorized/2 calls rabbit_mgmt_util:is_authorized/2, which checks only the management tag, instead of is_authorized_vhost/2. The /api/queues/quorum/:vhost/:queue/status handler reads the vhost from the path without checking that the user can access it. Any management-tagged user can therefore read Raft status, including leader, members, term, and commit index, for quorum queues in inaccessible vhosts, exposing cross-tenant queue names and cluster topology. The management plugin must be enabled and the attacker must have a management tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

CVSS Base Scores

version 3.1