cve.bz

CVE-2026-67419 broadcom rabbitmq server: Inefficient Algorithmic Complexity

7.1 highExploit referenceEPSS 0.4%Fix available

High (7.1) in broadcom rabbitmq server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.1 high
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

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-09-25. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-407 Inefficient Algorithmic Complexity
CWE-1333 Inefficient Regular Expression Complexity
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-67419 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67419?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67419?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67419 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
broadcom:rabbitmq_serverfrom 4.3.0 before 4.3.5

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14rabbitmq-server4.3.6-1DEBIAN-CVE-2026-67419
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 morerabbitmq-serverno fix listedUBUNTU-CVE-2026-67419
Red Hathummingbird:1rabbitmq-server4.30:4.3.6-1.hum1RHSA-2026:67552
Azure Linux3rabbitmq-server3.13.7-10AZL-104925

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This flaw is rated as Moderate severity because exploitation requires an authenticated client with permissions to declare queue bindings on a topic exchange and publish messages through it. In typical Red Hat environments such as Red Hat OpenStack Platform, RabbitMQ operates on internal networks with tightly managed service credentials, limiting the pool of potential attackers to trusted accounts. However, an authorized tenant or compromised credential could craft binding keys containing consecutive multi-segment wildcard tokens (`#`), causing the broker to perform exponential pattern-matching work during message routing. The resulting CPU exhaustion degrades or halts message delivery for all tenants sharing the affected broker instance.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Hardened Imagesrabbitmq-server4-3-main-4.3.6-1.hum1Fixed 2026-09-15RHSA-2026:67552
Red Hat Hardened Imagesrabbitmq-server4.2Will not fix
Red Hat OpenStack Platform 13 (Queens)rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 16.2rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 17.1rabbitmq-serverOut of support scope
Red Hat OpenStack Platform 18.0rabbitmq-serverFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-67419.

Attack patterns (CAPEC)

  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON