CVE-2026-67413

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2026-87228 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: No code on recordExposed 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.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 25, 2026

Last Modified

October 16, 2026

Advisory Details (7)

Auto-updated Sep 25, 2026
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 advisoryMentions a patch (unverified)

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(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.6-1.hum12026-09-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server3.10.8-1.1 ... 4.3.6-1 (29 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.6-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.2-5 (16 versions)
  • every version up to 4.3.6-1: fixed in 4.3.6-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-30 07:55 UTCOSV refresh
  16. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-25 14:10 UTCEchelonGraph re-scored
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  23. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  24. 2026-10-22 19:34 UTCEchelonGraph re-scored
  25. 2026-10-22 19:34 UTCVendor advisory
Show 61 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-10-18 03:20 UTCEchelonGraph re-scored
  7. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-16 16:13 UTCEchelonGraph re-scored▲ 0.50
  10. 2026-10-16 16:05 UTCNVD updateCVSS v3 → 6.5
  11. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  13. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-12 15:45 UTCEchelonGraph re-scored
  16. 2026-10-12 01:19 UTCVendor advisory
  17. 2026-10-11 19:30 UTCEchelonGraph re-scored
  18. 2026-10-11 16:46 UTCEchelonGraph re-scored
  19. 2026-10-11 14:06 UTCEchelonGraph re-scored
  20. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  21. 2026-10-10 21:51 UTCEchelonGraph re-scored
  22. 2026-10-10 21:51 UTCVendor advisory
  23. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-09 19:22 UTCEchelonGraph re-scored
  26. 2026-10-09 19:22 UTCVendor advisory
  27. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  28. 2026-10-08 16:56 UTCEchelonGraph re-scored
  29. 2026-10-08 16:56 UTCVendor advisory
  30. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  31. 2026-10-07 13:18 UTCEchelonGraph re-scored
  32. 2026-10-07 13:18 UTCVendor advisory
  33. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  34. 2026-10-06 10:54 UTCEchelonGraph re-scored
  35. 2026-10-06 10:54 UTCVendor advisory
  36. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  37. 2026-10-05 08:31 UTCEchelonGraph re-scored
  38. 2026-10-05 08:31 UTCVendor advisory
  39. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  40. 2026-10-04 06:07 UTCEchelonGraph re-scored
  41. 2026-10-04 06:07 UTCVendor advisory
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  43. 2026-10-03 03:43 UTCEchelonGraph re-scored
  44. 2026-10-03 03:43 UTCVendor advisory
  45. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-10-02 01:18 UTCEchelonGraph re-scored
  47. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-09-30 22:55 UTCEchelonGraph re-scored
  49. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-09-29 20:31 UTCEchelonGraph re-scored
  51. 2026-09-29 19:38 UTCEchelonGraph re-scored
  52. 2026-09-29 17:08 UTCEchelonGraph re-scored
  53. 2026-09-28 14:44 UTCEchelonGraph re-scored
  54. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  55. 2026-09-27 22:24 UTCEchelonGraph re-scored
  56. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  57. 2026-09-26 20:00 UTCEchelonGraph re-scored
  58. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  59. 2026-09-25 17:33 UTCEchelonGraph re-scored
  60. 2026-09-25 16:39 UTCEchelonGraph re-scoredFirst assessed: 6.0 MEDIUM
  61. 2026-09-25 16:39 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67413?
CVE-2026-67413 is a medium-severity vulnerability; its CVE record was 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 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…
When was the CVE record for CVE-2026-67413 published?
The CVE record for CVE-2026-67413 was published on September 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-67413 actively exploited?
CVE-2026-67413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67413?
CVE-2026-67413 has a CVSS v3 base score of 6.5 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs