Back to CVE records
High 7.1Published Sep 25, 2026

CVE-2026-67419RabbitMQ: Consecutive topic wildcards cause combinatorial routing work

Updated under an hour ago ()

Does this affect you?

It affects rabbitmq-server and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

RabbitMQ is a messaging and streaming broker. Prior to 4.3.5, an authenticated user who can bind a queue to a topic exchange and publish to it can use consecutive # segments in a binding key to make both topic matchers revisit the same trie-node and routing-key-suffix states without memoization. The matcher materializes duplicate destinations before deduplication, causing combinatorial CPU work and memory pressure that can disrupt routing for all tenants. This vulnerability is fixed in 4.3.5.

CVSS
7.1 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-407, CWE-1333
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Sep 25, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
rabbitmq rabbitmq-server
rabbitmq:server (from the name)
before 4.3.5
CNA record
broadcom rabbitmq_server
broadcom:rabbitmq_server
from 4.3.0 before 4.3.5
NVD

References

  • x-refsource-confirm, vendor-advisory, exploit, mitigation
  • x-refsource-misc, patch
  • x-refsource-misc, release-notes

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.