Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 10 Nov 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 16 Oct 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Broadcom
Broadcom rabbitmq Server |
|
| CPEs | cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Broadcom
Broadcom rabbitmq Server |
|
| Metrics |
cvssV3_1
|
Sat, 26 Sep 2026 12:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rabbitmq
Rabbitmq rabbitmq-server |
|
| Vendors & Products |
Rabbitmq
Rabbitmq rabbitmq-server |
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
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-25T17:01:50.884Z
Reserved: 2026-07-29T15:02:20.412Z
Link: CVE-2026-67419
Updated: 2026-09-25T17:01:45.510Z
Status : Analyzed
Published: 2026-09-25T17:17:13.830
Modified: 2026-10-16T15:46:33.137
Link: CVE-2026-67419
No data.
OpenCVE Enrichment
Updated: 2026-09-26T12:15:04Z