Skip to main content
VulnerabilityPublished Updated

CVE-2026-66067: RabbitMQ · Stream protocol skips per vhost per user connection limits

Affects rabbitmqSource GCVE Database

0
Compare
Authoritative record:CVE-2026-66067· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 4.3.1 or 4.2.7 when convenient.

Data as of 17 Nov 2026, 16:19 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.3.1, 4.2.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade rabbitmq to 4.3.1 or 4.2.7.

Affected software

ProductAffectedFixed in
Bitnamirabbitmqpkg:bitnami/rabbitmqOther threatsAffected
  • >=4.2.0 <4.2.7
  • >=4.3.0 <4.3.1
Fixed in
  • 4.2.7
  • 4.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade RabbitMQ to version 4.2.7 or 4.3.1 or later, where this vulnerability is fixed. Operators relying on per-user and per-vhost connection limits should ensure they are running a patched version. No other mitigations are indicated.

Description

RabbitMQ versions prior to 4.2.7 and 4.3.1 have a vulnerability in the stream protocol where per-vhost and per-user connection limits are bypassed. The stream open handler does not enforce these connection caps, allowing authenticated tenants to exceed operator-configured limits by connecting via port 5552 instead of the standard AMQP port 5672. This issue is fixed in versions 4.2.7 and 4.3.1.

References

Community reviews

Loading reviews…