CVE-2026-66067
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
3- cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*Range: >=4.2.0,<4.2.7
- Range: <4.2.7, <4.3.1
Patches
Vulnerability mechanics
References
3- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-hwqx-2gfg-89qfnvdVendor Advisory
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7nvdRelease Notes
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1nvdRelease Notes
News mentions
1- RabbitMQ Server: 22 Vulnerabilities Disclosed Together, Ranging from Critical to Low SeverityVypr Intelligence · Sep 23, 2026