Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 25 Sep 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | RabbitMQ: Consecutive topic wildcards cause combinatorial routing work | |
| Weaknesses | CWE-1333 CWE-407 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-25T17:01:50.884Z
Reserved: 2026-07-29T15:02:20.412Z
Link: CVE-2026-67419
No data.
Status : Received
Published: 2026-09-25T17:17:13.830
Modified: 2026-09-25T18:17:30.443
Link: CVE-2026-67419
No data.
OpenCVE Enrichment
No data.