RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
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.
- Products
- rabbitmq
- Affected versions
- Not specified
- Fixed versions
- 4.3.5
- CVEs
- CVE-2026-67419
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 23:59 UTC · Revision 1
Source evidence
RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
core-osv · Original sourcePublished 1 Oct 2026, 09:33 UTC
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.
osv:BIT-rabbitmq-2026-67419
rabbitmq
Fixed versions: 4.3.5
Complete source record
{
"id": "21bbfe0e639ca56803d4687bd67a91782ebb59afdb47cc78f376bcbbdcb6bfc9",
"url": "https://osv.dev/vulnerability/BIT-rabbitmq-2026-67419",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ: Consecutive topic wildcards cause combinatorial routing work",
"summary": "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.",
"evidence": "osv:BIT-rabbitmq-2026-67419",
"products": [
{
"name": {
"value": "rabbitmq",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.3.5",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "BIT-rabbitmq-2026-67419",
"aliases": [
"BIT-rabbitmq-2026-67419",
"CVE-2026-67419",
"GHSA-h964-v5mf-22cq"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "4.3.5"
}
]
}
],
"package": {
"name": "rabbitmq",
"purl": "pkg:bitnami/rabbitmq",
"ecosystem": "Bitnami"
},
"severity": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"database_specific": {
"source": "https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-67419.json"
}
}
],
"modified": "2026-10-17T09:15:02.456671235Z",
"provider": "osv",
"references": [
"https://github.com/rabbitmq/rabbitmq-server/commit/c5ed7c4e97e02be688730803604cc7a88dbe4864",
"https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-22cq",
"https://nvd.nist.gov/vuln/detail/CVE-2026-67419"
],
"provider_metadata": {
"cpes": [
"cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*"
],
"severity": "High"
}
},
"related_cves": [
{
"value": "CVE-2026-67419",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 352248,
"published_at": "2026-10-01T09:33:57.784+00:00"
}