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

> An authenticated user can cause denial of service in RabbitMQ by using consecutive topic wildcards in binding keys, leading to excessive CPU and memory usage.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** AZL-104925, BIT-rabbitmq-2026-67419, DEBIAN-CVE-2026-67419, GHSA-h964-v5mf-22cq, UBUNTU-CVE-2026-67419

## What is CVE-2026-67419?

CVE-2026-67419 is a high-severity denial of service vulnerability in Broadcom Rabbitmq Server, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-407 (Inefficient Algorithmic Complexity), CWE-1333 (Inefficient Regular Expression Complexity)

## Which versions are affected by CVE-2026-67419?

1 open source package ship an affected version, including rabbitmq. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rabbitmq` | Bitnami | All versions | 4.3.5 |

Products: Broadcom Rabbitmq Server.

## How do I fix CVE-2026-67419?

Upgrade rabbitmq to 4.3.5 or later.

## Is CVE-2026-67419 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67419 exists.

## Other vulnerabilities in Broadcom Rabbitmq Server

- [CVE-2016-9877](https://insights.sbomify.com/CVE-2016-9877/): Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7 (critical 9.8)
- [CVE-2026-67404](https://insights.sbomify.com/CVE-2026-67404/): RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch (critical 9.2)
- [CVE-2026-67231](https://insights.sbomify.com/CVE-2026-67231/): RabbitMQ: Trust-store whitelist by Issuer+Serial only (critical 9.1)
- [CVE-2026-57219](https://insights.sbomify.com/CVE-2026-57219/): Information disclosure in rabbitmq-server (high 8.7)
- [CVE-2026-67236](https://insights.sbomify.com/CVE-2026-67236/): RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-67419 and fix it if it is affected.

What it is: CVE-2026-67419 is a high-severity denial of service vulnerability in Broadcom Rabbitmq Server, published on 25 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67419 exists.

Affected packages and fixed versions:
- rabbitmq (Bitnami): affected all versions; fixed in 4.3.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-67419/ (Markdown: https://insights.sbomify.com/CVE-2026-67419/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-67419
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-67419
- OSV: https://osv.dev/vulnerability/CVE-2026-67419

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-67419/
Summaries are generated and may contain mistakes; the official description above is the record.