Vulnerability in RabbitMQ (CVE-2026-67419)
Summary
Vulnerability in RabbitMQ (CVE-2026-67419). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.3.5 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-67419 has been found in RabbitMQ.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade RabbitMQ to 4.3.5 or later.
If unsure, ask your IT team or search "RabbitMQ CVE-2026-67419" on the vendor's site.
CVE-2026-67419 (RabbitMQ) — CWE-407 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.3.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-407) exists in RabbitMQ.
Check the vendor advisory for the affected versions of RabbitMQ.
Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.
Update to 4.3.5.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'RabbitMQ' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'RabbitMQ' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
RabbitMQを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade RabbitMQ to 4.3.5ステージング環境で 4.3.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-67419 rabbitmq-server Fixed in: 4.3.6-1
- Ubuntu UBUNTU-CVE-2026-67419 rabbitmq-server
References
- advisory github.com
- patch github.com
- web github.com
- web nvd.nist.gov