CVE-2026-67419

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
48
EG Risk 48/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 28, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

RabbitMQ 4.3.5

Patch available: rabbitmq/rabbitmq-server v4.3.5

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.5
github_commit

commit c5ed7c4e97e0 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit c5ed7c4e97e0 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/c5ed7c4e97e02be688730803604cc7a88dbe4864
github Patch Available🟡 PoC Available

Consecutive topic wildcards cause combinatorial routing work · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-h964-v5mf-22cq

Vendor Advisories for CVE-2026-67419(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 06:56 UTCVendor advisory
  2. 2026-10-03 19:36 UTCEG score recompute
  3. 2026-10-03 19:36 UTCVendor advisory
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 08:17 UTCVendor advisory
  6. 2026-10-02 20:52 UTCEG score recompute
  7. 2026-10-02 20:52 UTCVendor advisory
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-02 09:32 UTCVendor advisory
  10. 2026-10-01 22:12 UTCEG score recompute
  11. 2026-10-01 22:12 UTCVendor advisory
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 10:49 UTCVendor advisory
  14. 2026-09-30 23:29 UTCEG score recompute
  15. 2026-09-30 23:29 UTCVendor advisory
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-30 12:07 UTCVendor advisory
  18. 2026-09-30 00:45 UTCEG score recompute
  19. 2026-09-30 00:45 UTCVendor advisory
  20. 2026-09-29 13:25 UTCVendor advisory
  21. 2026-09-29 02:04 UTCEG score recompute
  22. 2026-09-28 14:44 UTCEG score recompute
  23. 2026-09-28 13:52 UTCEPSS rescore
  24. 2026-09-27 16:07 UTCEG score recompute
  25. 2026-09-27 13:48 UTCEPSS rescore
Show 6 more
  1. 2026-09-26 17:22 UTCEG score recompute
  2. 2026-09-26 15:59 UTCEPSS rescore
  3. 2026-09-25 18:39 UTCEG score recompute
  4. 2026-09-25 17:19 UTCEG score recompute
  5. 2026-09-25 16:50 UTCEG score recompute
  6. 2026-09-25 16:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67419?
CVE-2026-67419 is a high vulnerability published on September 25, 2026. 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.…
When was CVE-2026-67419 disclosed?
CVE-2026-67419 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67419 actively exploited?
CVE-2026-67419 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67419?
CVE-2026-67419 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67419?
A fix for CVE-2026-67419 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67419 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-67419

Explore →

Is Your Infrastructure Affected by CVE-2026-67419?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs