CVE-2026-67405

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st 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
Trending — 3 sources updated this week

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

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.1Exploit: 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, Neither the Web-MQTT handler (deps/rabbitmq_web_mqtt/src/rabbit_web_mqtt_handler.erl:104) nor the Web-STOMP handler (deps/rabbitmq_web_stomp/src/rabbit_web_stomp_handler.erl:102) validates the Origin header on the WebSocket upgrade. Under ssl_cert_login=true, the browser presents the client certificate automatically, so an attacker's JavaScript running in the victim's browser can authenticate as the victim. Preconditions include The non-default configuration use_http_auth=true (Web-STOMP) or ssl_cert_login=true (both plugins) must be enabled. The issue is harmless under the default in-band CONNECT credential configuration.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
36
EG Risk 36/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
1st
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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)

CSWSH on Web-STOMP / Web-MQTT (no Origin validation) · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-9c4f-rxxm-88q3

Vendor Advisories for CVE-2026-67405(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.2-5 (28 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-server4.0.5-10 ... 4.3.2-5 (18 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 8× in last 7d / 54× 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.1% · 1st percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-29 16:40 UTCEG score recompute
  5. 2026-10-29 16:40 UTCVendor advisory
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-25 14:10 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-22 11:32 UTCEG score recompute
  15. 2026-10-22 11:32 UTCVendor advisory
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-19 20:22 UTCEG score recompute▲ 2.80
  19. 2026-10-19 20:22 UTCVendor advisory
  20. 2026-10-19 19:45 UTCNVD updateCVSS v3 → 8.1 · severity → HIGH
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-18 03:20 UTCEG score recompute
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 55 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-12 15:45 UTCEG score recompute
  4. 2026-10-11 22:45 UTCVendor advisory
  5. 2026-10-11 19:30 UTCEG score recompute
  6. 2026-10-11 16:46 UTCEG score recompute
  7. 2026-10-11 14:07 UTCEG score recompute
  8. 2026-10-10 20:51 UTCEG score recompute
  9. 2026-10-10 20:51 UTCVendor advisory
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-09 18:57 UTCEG score recompute
  13. 2026-10-09 18:57 UTCVendor advisory
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-08 17:03 UTCEG score recompute
  16. 2026-10-08 17:03 UTCVendor advisory
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-07 14:20 UTCEG score recompute
  19. 2026-10-07 14:20 UTCVendor advisory
  20. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-10-06 12:08 UTCEG score recompute
  22. 2026-10-06 12:08 UTCVendor advisory
  23. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-10-05 10:14 UTCEG score recompute
  25. 2026-10-05 10:14 UTCVendor advisory
  26. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  27. 2026-10-04 08:21 UTCEG score recompute
  28. 2026-10-04 08:21 UTCVendor advisory
  29. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-10-03 06:27 UTCEG score recompute
  31. 2026-10-03 06:27 UTCVendor advisory
  32. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  33. 2026-10-02 04:33 UTCEG score recompute
  34. 2026-10-02 04:33 UTCVendor advisory
  35. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  36. 2026-10-01 02:36 UTCEG score recompute
  37. 2026-10-01 02:36 UTCVendor advisory
  38. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  39. 2026-09-30 00:43 UTCEG score recompute
  40. 2026-09-30 00:43 UTCVendor advisory
  41. 2026-09-28 22:48 UTCEG score recompute
  42. 2026-09-28 22:48 UTCVendor advisory
  43. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-09-27 20:54 UTCEG score recompute
  45. 2026-09-27 20:54 UTCVendor advisory
  46. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-09-26 19:00 UTCEG score recompute
  48. 2026-09-26 19:00 UTCVendor advisory
  49. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  50. 2026-09-25 17:02 UTCVendor advisory
  51. 2026-09-24 14:34 UTCEG score recompute
  52. 2026-09-24 14:17 UTCEG score recompute
  53. 2026-09-23 21:22 UTCEG score recompute
  54. 2026-09-23 20:43 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  55. 2026-09-23 20:43 UTCMITRE cvelistV5first tracked

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

Frequently asked(5)

What is CVE-2026-67405?
CVE-2026-67405 is a high-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, Neither the Web-MQTT handler (deps/rabbitmq_web_mqtt/src/rabbit_web_mqtt_handler.erl:104) nor the Web-STOMP handler (deps/rabbitmq_web_stomp/src/rabbit_web_stomp_handler.erl:102) validates the…
When was the CVE record for CVE-2026-67405 published?
The CVE record for CVE-2026-67405 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-67405 actively exploited?
CVE-2026-67405 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67405?
CVE-2026-67405 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-67405?
A fix for CVE-2026-67405 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67405 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-67405

Explore →

Is Your Infrastructure Affected by CVE-2026-67405?

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

Book a Demo →Browse All CVEs