CVE-2026-67219

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.3% (23rd 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

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

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, add_binding/3 parses the routing key as an integer weight N and computes ring positions with lists:seq(NextN0, NextN0 + N - 1). validate_binding/2 only checks N >= 1 , no upper bound. The resulting list is stored in the exchange's Khepri record, replicated cluster-wide, and reloaded on restart. A user with write permission on a consistent-hash exchange and read on a queue can create a binding whose routing key (the hash-ring weight) is an arbitrarily large integer. The broker allocates a list of that many integers via lists:seq/2 and persists it to Khepri across all cluster nodes , a single binding with weight 100000000 allocates ~800 MB on every node and survives restarts. Preconditions include rabbitmq_consistent_hash_exchange plugin enabled write permission on a consistent-hash exchange + read on a queue (standard binding perms). This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.3%
EPSS %ILE
23rd
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 every mission impact level.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 every mission impact level.

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

Exploitation none (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 23, 2026

Last Modified

October 19, 2026

Advisory Details (3)

Auto-updated Sep 23, 2026
Patch available. Sources: github, github_release.
GitHub release Patch Available

RabbitMQ 4.3.0

Patch available: rabbitmq/rabbitmq-server v4.3.0

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0
GitHub release Patch Available

RabbitMQ 4.2.6

Patch available: rabbitmq/rabbitmq-server v4.2.6

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
GitHub advisoryMentions a patch (unverified)

Consistent-hash exchange unbounded weight · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-m8pg-4x2h-jvgr

Vendor Advisories for CVE-2026-67219(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.0-1 (9 versions)
  • every version up to 4.3.0-2: fixed in 4.3.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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.3% · 23rd percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  9. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  10. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  11. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  13. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  14. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  15. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  16. 2026-10-29 14:43 UTCEchelonGraph re-scored
  17. 2026-10-29 14:43 UTCVendor advisory
  18. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  19. 2026-10-28 12:55 UTCOSV refresh
  20. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  21. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  22. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  23. 2026-10-25 14:10 UTCEchelonGraph re-scored
  24. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  25. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
Show 74 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-19 20:47 UTCEchelonGraph re-scored▲ 0.50
  5. 2026-10-19 20:47 UTCVendor advisory
  6. 2026-10-19 20:45 UTCNVD updateCVSS v3 → 6.5
  7. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  8. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  9. 2026-10-18 03:20 UTCEchelonGraph re-scored
  10. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  11. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  13. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  14. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  15. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  16. 2026-10-12 15:46 UTCEchelonGraph re-scored
  17. 2026-10-11 19:30 UTCEchelonGraph re-scored
  18. 2026-10-11 16:46 UTCEchelonGraph re-scored
  19. 2026-10-11 13:53 UTCEchelonGraph re-scored
  20. 2026-10-11 13:53 UTCVendor advisory
  21. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-10 15:15 UTCEchelonGraph re-scored
  24. 2026-10-10 15:15 UTCVendor advisory
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  26. 2026-10-09 16:42 UTCVendor advisory
  27. 2026-10-08 18:09 UTCEchelonGraph re-scored
  28. 2026-10-08 18:09 UTCVendor advisory
  29. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  30. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  31. 2026-10-07 19:35 UTCVendor advisory
  32. 2026-10-06 21:01 UTCEchelonGraph re-scored
  33. 2026-10-06 21:01 UTCVendor advisory
  34. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  35. 2026-10-05 22:24 UTCEchelonGraph re-scored
  36. 2026-10-05 22:24 UTCVendor advisory
  37. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  38. 2026-10-04 23:51 UTCEchelonGraph re-scored
  39. 2026-10-04 23:51 UTCVendor advisory
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-10-04 01:17 UTCEchelonGraph re-scored
  42. 2026-10-04 01:17 UTCVendor advisory
  43. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  44. 2026-10-03 02:43 UTCEchelonGraph re-scored
  45. 2026-10-03 02:43 UTCVendor advisory
  46. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  47. 2026-10-02 04:10 UTCEchelonGraph re-scored
  48. 2026-10-02 04:10 UTCVendor advisory
  49. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  50. 2026-10-01 05:32 UTCEchelonGraph re-scored
  51. 2026-10-01 05:32 UTCVendor advisory
  52. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  53. 2026-09-30 07:00 UTCEchelonGraph re-scored
  54. 2026-09-30 07:00 UTCVendor advisory
  55. 2026-09-29 08:27 UTCEchelonGraph re-scored
  56. 2026-09-29 08:27 UTCVendor advisory
  57. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  58. 2026-09-28 09:54 UTCEchelonGraph re-scored
  59. 2026-09-28 09:54 UTCVendor advisory
  60. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  61. 2026-09-27 11:21 UTCEchelonGraph re-scored
  62. 2026-09-27 11:21 UTCVendor advisory
  63. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  64. 2026-09-26 12:46 UTCEchelonGraph re-scored
  65. 2026-09-26 12:46 UTCVendor advisory
  66. 2026-09-25 14:08 UTCVendor advisory
  67. 2026-09-24 15:29 UTCVendor advisory
  68. 2026-09-24 15:08 UTCEchelonGraph re-scored
  69. 2026-09-24 15:08 UTCVendor advisory
  70. 2026-09-24 14:50 UTCEchelonGraph re-scored
  71. 2026-09-24 14:50 UTCVendor advisory
  72. 2026-09-23 21:22 UTCEchelonGraph re-scored
  73. 2026-09-23 20:43 UTCEchelonGraph re-scoredFirst assessed: 6.0 MEDIUM
  74. 2026-09-23 20:43 UTCMITRE cvelistV5first tracked

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

Frequently asked(5)

What is CVE-2026-67219?
CVE-2026-67219 is a medium-severity vulnerability; its CVE record was published on September 23, 2026. RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, add_binding/3 parses the routing key as an integer weight N and computes ring positions with lists:seq(NextN0, NextN0 + N - 1). validate_binding/2 only checks N >= 1 , no upper bound. The…
When was the CVE record for CVE-2026-67219 published?
The CVE record for CVE-2026-67219 was published on September 23, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-67219 actively exploited?
CVE-2026-67219 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-67219?
CVE-2026-67219 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-67219?
A fix for CVE-2026-67219 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67219 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-67219

Explore →

Is Your Infrastructure Affected by CVE-2026-67219?

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

Book a Demo →Browse All CVEs