CVE-2026-67413

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th 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
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.0Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.23, 4.1.14, 4.2.9, and 4.3.3, the optional rabbitmq_jms_topic_exchange plugin's x-jms-topic exchange accepted a client-controlled rjms_erlang_selector binding expression whose LIKE evaluator expanded percent and underscore wildcards into overlapping PCRE fragments. It executed those fragments with raw re:run/3 without match or recursion limits, allowing an authenticated tenant that can bind and publish to consume broker scheduler CPU and deny service with pathological selectors. This issue is fixed in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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
Severity60% × 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
20th
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 29, 2026

Advisory Details (7)

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

RabbitMQ 4.3.3

Patch available: rabbitmq/rabbitmq-server v4.3.3

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
github_release Patch Available

RabbitMQ 4.2.9

Patch available: rabbitmq/rabbitmq-server v4.2.9

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

commit f4d9da668b73 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/f4d9da668b7304dfb9aeb2b4e9ff766a1275d021
github_commit

commit 9e36b7f4c1e2 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/9e36b7f4c1e2eed77300288dca3e01bd9b23c432
github_commit

commit 60de2fbbcd81 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/60de2fbbcd812ab294985cef260cc2f1b1a02a5b
github_commit

commit 20203c50ea6f (rabbitmq/rabbitmq-server)

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

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

Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an Unbounded LIKE Regular Expression · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-chxf-3hfg-j8f7

Vendor Advisories for CVE-2026-67413(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 22× 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:07 UTCEG score recompute
  2. 2026-10-04 06:07 UTCVendor advisory
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-03 03:43 UTCEG score recompute
  5. 2026-10-03 03:43 UTCVendor advisory
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 01:18 UTCEG score recompute
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 22:55 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-29 20:31 UTCEG score recompute
  12. 2026-09-29 19:38 UTCEG score recompute
  13. 2026-09-29 17:08 UTCEG score recompute
  14. 2026-09-28 14:44 UTCEG score recompute
  15. 2026-09-28 13:52 UTCEPSS rescore
  16. 2026-09-27 22:24 UTCEG score recompute
  17. 2026-09-27 13:48 UTCEPSS rescore
  18. 2026-09-26 20:00 UTCEG score recompute
  19. 2026-09-26 15:59 UTCEPSS rescore
  20. 2026-09-25 17:33 UTCEG score recompute
  21. 2026-09-25 16:39 UTCEG score recompute
  22. 2026-09-25 16:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67413?
CVE-2026-67413 is a medium vulnerability published on September 25, 2026. RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.23, 4.1.14, 4.2.9, and 4.3.3, the optional rabbitmqjmstopicexchange plugin's x-jms-topic exchange accepted a client-controlled rjmserlang_selector binding expression whose LIKE evaluator expanded percent and underscore wildcards…
When was CVE-2026-67413 disclosed?
CVE-2026-67413 was first published on September 25, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67413 actively exploited?
CVE-2026-67413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67413?
CVE-2026-67413 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67413?
A fix for CVE-2026-67413 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67413 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-67413?

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