CVSS 4.0
7.1 highCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NHigh (7.1) in broadcom rabbitmq server. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| broadcom:rabbitmq_server | from 4.3.0 before 4.3.5 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | rabbitmq-server | 4.3.6-1 | DEBIAN-CVE-2026-67419 |
| Ubuntu | 22.04:LTS, 24.04:LTS, 26.04:LTS and 4 more | rabbitmq-server | no fix listed | UBUNTU-CVE-2026-67419 |
| Red Hat | hummingbird:1 | rabbitmq-server4.3 | 0:4.3.6-1.hum1 | RHSA-2026:67552 |
| Azure Linux | 3 | rabbitmq-server | 3.13.7-10 | AZL-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 rates this Moderate.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | rabbitmq-server4-3-main-4.3.6-1.hum1 | Fixed 2026-09-15 | RHSA-2026:67552 |
| Red Hat Hardened Images | rabbitmq-server4.2 | Will not fix | |
| Red Hat OpenStack Platform 13 (Queens) | rabbitmq-server | Out of support scope | |
| Red Hat OpenStack Platform 16.2 | rabbitmq-server | Out of support scope | |
| Red Hat OpenStack Platform 17.1 | rabbitmq-server | Out of support scope | |
| Red Hat OpenStack Platform 18.0 | rabbitmq-server | Fix 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.