Skip to content
Heist/ feed
Back to feed
High

RabbitMQ: Consecutive topic wildcards cause combinatorial routing work

Type: advisorySources: OSV

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
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2026-67419
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 16:44 UTC · Revision 1

Source evidence

RabbitMQ: Consecutive topic wildcards cause combinatorial routing work

core-osv · Original source

Published 25 Sept 2026, 16:41 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:CVE-2026-67419
Complete source record
{
  "id": "ee5e698ea1c127ff35d82c9279b96ddd06d9d26783dffde63a588dae4a2b28dd",
  "url": "https://osv.dev/vulnerability/CVE-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:CVE-2026-67419",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-67419",
      "aliases": [
        "BIT-rabbitmq-2026-67419",
        "CVE-2026-67419",
        "GHSA-h964-v5mf-22cq"
      ],
      "metrics": [
        {
          "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"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/rabbitmq/rabbitmq-server",
              "type": "GIT",
              "events": [
                {
                  "introduced": "1929eeadf9b2bac12c5434fb56884ef27370580e"
                },
                {
                  "fixed": "0dde27bfdd1984ff7e157226fd97656854a7f359"
                },
                {
                  "fixed": "c5ed7c4e97e02be688730803604cc7a88dbe4864"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "4.3.0"
                      },
                      {
                        "fixed": "4.3.5"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "range": [
                      {
                        "fixed": "c5ed7c4e97e02be688730803604cc7a88dbe4864"
                      }
                    ],
                    "source": "REFERENCES_COMMIT"
                  },
                  {
                    "range": [
                      {
                        "fixed": "0dde27bfdd1984ff7e157226fd97656854a7f359"
                      }
                    ],
                    "source": "REFERENCES_TAG",
                    "original_tag": "v4.3.5"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v4.3.4",
            "v4.3.3",
            "v4.3.2",
            "v4.3.1",
            "v4.3.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-67419.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:44.388589680Z",
      "provider": "osv",
      "references": [
        "https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67419.json",
        "https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-22cq",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-67419",
        "https://github.com/rabbitmq/rabbitmq-server/commit/c5ed7c4e97e02be688730803604cc7a88dbe4864"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-1333",
          "CWE-407"
        ],
        "cna_assigner": "GitHub_M",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/67xxx/CVE-2026-67419.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-67419",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 512441,
  "published_at": "2026-09-25T16:41:08.104+00:00"
}