Insufficient Granularity of Access Control 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.35% (26th 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-20073396
  • published24 Sept 2026
  • disclosed23 Sept 2026

Introduced: 23 Sep 2026

NewCVE-2026-66067  (opens in a new tab)
CWE-1220  (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 4.2.7 and 4.3.1, The stream open handler calls only check_vhost_access; it omits the node/vhost/user connection-limit checks that rabbit_reader performs for AMQP. A developer %% FIXME comment at the cited line explicitly acknowledges the gap. No compensating enforcement exists in connection tracking or elsewhere in rabbitmq_stream. An authenticated tenant can fully bypass operator-configured per-user and per-vhost connection caps by connecting via port 5552 instead of 5672. Preconditions include rabbitmq_stream plugin enabled Authenticated stream-protocol credentials Operator relies on per-user/per-vhost connection limits for tenant isolation. This issue is fixed in versions 4.2.7 and 4.3.1.

CVSS Base Scores

version 3.1