ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-67419

RabbitMQ: Consecutive topic wildcards cause combinatorial routing work

Published Oct 1, 2026 · catalog updated Oct 17, 2026 · RabbitMQ: Consecutive topic wildcards

Check if you run it

No confirmed exploitation is on record for CVE-2026-67419. EPSS is 0.37%. Act only if a listed version of RabbitMQ: Consecutive topic wildcards is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (RabbitMQ: Consecutive topic wildcards).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.37%
Remediation
Advisory link
Affected products
Bitnami rabbitmq

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Bitnami rabbitmq0 → 4.3.5

How to fix CVE-2026-67419

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-67419. EPSS is 0.37%. Act only if a listed version of RabbitMQ: Consecutive topic wildcards is installed.

Which versions are affected?

Compare what you have installed with 0 → 4.3.5. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 1, 2026 · GitHub Advisory Database

    Detected

    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 an

  2. Oct 17, 2026 · GitHub Advisory Database

    Fix available

    rabbitmq fixed in 4.3.5

  3. Oct 17, 2026 · GitHub Advisory Database

    Fix available

    rabbitmq fixed in 4.3.5

  4. Oct 17, 2026 · GitHub Advisory Database

    Updated

    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 an

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.