Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-67419: RabbitMQ is a messaging and streaming broker

35
Routine
MEDIUM 6.5UPGRADE

CVE-2026-67419 is a medium-severity flaw (CVSS 6.5) affecting rabbitmq server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.4% (top 69%)
CISA exploited listNo
WeaknessCWE-407, CWE-1333
Published2026-09-25
Last modified2026-10-16
Publisher (CNA): GitHub, Inc. · Vendor: broadcom

Share: LinkedIn · X · Reddit

Last updated 2026-10-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

broadcom rabbitmq server UPGRADE
Affected: >= 4.3.0 and < 4.3.5
Fixed in: 4.3.5
Safe to downgrade to: a release before 4.3.0
1. Check installed version
apt-cache policy rabbitmq-server || rpm -q rabbitmq-server || rabbitmq-server --version
2. UPGRADE to 4.3.5 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade rabbitmq-server
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade rabbitmq-server
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.3.0 (Debian / Ubuntu)
apt-cache madison rabbitmq-server sudo apt install rabbitmq-server=<VERSION_BEFORE_4.3.0> sudo apt-mark hold rabbitmq-server
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list rabbitmq-server sudo dnf downgrade rabbitmq-server-<VERSION_BEFORE_4.3.0> sudo dnf versionlock add rabbitmq-server
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-67419?

rabbitmq server: upgrade to 4.3.5. Exact commands for each OS are on this page.

Is CVE-2026-67419 being exploited?

CVE-2026-67419 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-67419 affect?

CVE-2026-67419 affects rabbitmq server. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2026-67419?

Priority 35/100. Public exploit reference

Software pages

RabbitMQ vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.