CVE-2026-67406

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% (27th 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-87240 (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. From 4.0.0 until 4.3.3, 4.2.9, 4.1.14, and 4.0.23, Shovel does not format state logged by the crash reporter and can leave unencrypted credentials in a crash dump file. the shovel worker genserver processes does not implement the formatstatus/2 callback. When these processes crash (e.g., due to network partitions, connection failures), the OTP SASL error handler writes the full process state , including plaintext AMQP passwords and URIs , to the error log. This is particularly severe for the shovel worker, which stores deobfuscated plaintext URIs (including amqp://user:password@host format) in its genserver state for the entire process Automatic Credential Exposure: Shovel worker crashes (common during network partitions) automatically write plaintext upstream/downstream passwords to error logs No Special Configuration Needed: Unlike DEBUG logging, SASL error reports are always active Broad. This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23.

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
27th
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. 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 25, 2026

Last Modified

October 16, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
Patch available. Sources: github, 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 advisoryMentions a patch (unverified)

Shovel does not format state logged by the crash reporter and can leave unencrypted credentials in a crash dump file · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q44f-9vc5-grh7

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 8× in last 7d / 58× 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 it from the CNA feed. 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). Most recent first.

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

Frequently asked(5)

What is CVE-2026-67406?
CVE-2026-67406 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.3.3, 4.2.9, 4.1.14, and 4.0.23, Shovel does not format state logged by the crash reporter and can leave unencrypted credentials in a crash dump file. the shovel worker genserver processes does not implement the formatstatus/2…
When was the CVE record for CVE-2026-67406 published?
The CVE record for CVE-2026-67406 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-67406 actively exploited?
CVE-2026-67406 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67406?
CVE-2026-67406 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-67406?
A fix for CVE-2026-67406 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67406 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-67406

Explore →

Is Your Infrastructure Affected by CVE-2026-67406?

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