CVE-2026-67419CWE-1333CWE-407

CVE-2026-67419

Medium · published September 25, 2026

CVSS v3.1
6.5
EPSS
0%
Percentile
30.0
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
6.5 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS v4.0
7.1 · 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
EPSS
0.00373 · 30.0th percentile
Weaknesses
CWE-1333 · Inefficient Regular Expression Complexity; CWE-407 · Inefficient Algorithmic Complexity
Published
2026-09-25T21:17Z
Affected products (1)
ProductVersionsFixed in
broadcom/rabbitmq_server≥ 4.3.0, < 4.3.54.3.5
References (4)
EPSS history
Timeline
  • 27 SEP 03:27Z
    EPSS moved — → 0%
    epss
  • 25 SEP 16:41Z
    RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
    cvelistv5