CVE-2026-66067Medium· 6.0▾ SunlitRabbitMQ 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 develope…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 33 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-67228Medium· 6.9RabbitMQ is a messaging and streaming broker
CVE-2026-67240Low· 2.3RabbitMQ is a messaging and streaming broker
CVE-2026-67238High· 7.1RabbitMQ is a messaging and streaming broker
CVE-2026-67235High· 7.1RabbitMQ is a messaging and streaming broker
CVE-2026-67219Medium· 6.0RabbitMQ is a messaging and streaming broker
CVE-2026-66075Low· 2.3RabbitMQ is a messaging and streaming broker