All vulnerabilities

Servers and applications

CVE-2026-67419

Consecutive topic wildcards cause combinatorial routing work

Severity
High 7.1
Published
18 Aug 2026
Last changed
16 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
Exploit chance
0.4% in the next 30 daysHigher than 31% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Inefficient algorithmic complexity (CWE-407)Regular expression denial of service (ReDoS) (CWE-1333)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Take it down
CVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-h964-v5mf-22cq
Sources
NVD, Project advisories (GitHub)

Description

An authenticated user who can bind a queue to a topic exchange and publish to that exchange can force the routing engine into combinatorial recursion by using a binding key that contains consecutive # segments.

When such a binding is matched against a routing key of comparable depth, the matcher repeatedly re-enters identical {trie node, remaining routing-key suffix} states without memoization, and builds a duplicate list of destination results that is only deduplicated after the full traversal completes.

A binding and routing key only tens of bytes long can therefore drive millions to billions of recursive matcher invocations and allocate a correspondingly large intermediate result list, all while producing exactly one queue delivery. The work is performed inline in the routing path with no connection, channel, queue, message-size, or memory-alarm limit interrupting a single in-progress traversal.

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Workarounds

There is no effective configuration-level mitigation. Any account able to bind and publish on a topic exchange can trigger the behavior, and there is no setting that bounds per-routing work or rejects consecutive-# binding keys. The only robust fix is at the code level.

Workarounds as given by rabbitmq/rabbitmq-server's security advisory.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 4.3.0 before 4.3.5
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 before 3.13.19
  • From 4.0.0 before 4.0.24
  • From 4.1.0 before 4.1.15
  • From 4.2.0 before 4.2.10
  • From 4.3.0 before 4.3.5

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67419
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67419
  • GitHub Advisory Database https://github.com/advisories/GHSA-h964-v5mf-22cq
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-22cq