Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67419)
Description
RabbitMQ versions prior to 4.3.5 contain a vulnerability where an authenticated user who can bind a queue to a topic exchange and publish to it can exploit consecutive '#' segments in a binding key. This causes the topic matchers to revisit the same trie-node and routing-key-suffix states without memoization, leading to duplicate destination materialization before deduplication. The resulting combinatorial CPU and memory load can disrupt routing for all tenants. This issue is fixed in version 4.3.5.
CVSS v4.0
Affected software
pkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/bionicpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/focalpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=jammypkg:deb/ubuntu/rabbitmq-server?arch=source&distro=noblepkg:deb/ubuntu/rabbitmq-server?arch=source&distro=stonkingpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-67419 affects RabbitMQ messaging broker versions prior to 4.3.5. An authenticated user with permissions to bind queues to topic exchanges and publish messages can craft binding keys with consecutive '#' segments. This triggers the topic matchers to revisit the same trie-node and routing-key-suffix states multiple times without memoization, causing the matcher to materialize duplicate destinations before deduplication. The excessive CPU and memory consumption can disrupt message routing for all tenants sharing the broker. The vulnerability is resolved in RabbitMQ version 4.3.5.
Potential Impact
The vulnerability can cause significant CPU and memory resource exhaustion on the RabbitMQ server, leading to disruption of message routing services for all tenants. This can degrade performance or cause denial of service conditions. Exploitation requires authenticated user privileges with queue binding and publishing capabilities.
Mitigation Recommendations
Upgrade RabbitMQ to version 4.3.5 or later, where this vulnerability is fixed. No other mitigations are specified. Patch status is confirmed as fixed in 4.3.5.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-67419
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.10","Ubuntu:26.04:LTS"]
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad3f5a72cdf04f6566627d3
Added to database: 10/17/2026, 22:24:39 UTC
Last enriched: 10/17/2026, 23:54:23 UTC
Last updated: 10/17/2026, 23:54:23 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.