CVE-2026-67241

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.4% (36th 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-87153 (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.4%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.2.0 until 4.2.9 and 4.3.3, AMQP 1.0 management exchange.declare skips alternate-exchange permission check. pUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbitexchange:declare/7. It omits the checkreadpermitted(X) + checkwritepermitted(AE) that rabbitchannel.erl:2540-2548 enforces for the alternate-exchange argument on the AMQP 0-9-1 path. The same file already implements the analogous DLX check for queues (lines 708-719), confirming this is a missing-check bug rather than intentional A user with only configure on exchange X can route X's unroutable messages into an alternate exchange they have no write permission AMQP 1.0 enabled (default in RabbitMQ 4.x) Attacker has configure on at least one exchange but lacks write on the target. This issue is fixed in versions 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.4%
EPSS %ILE
36th
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.4% 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 (5)

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 56005e7cebff (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/56005e7cebffc478ef397573de24aff1167e7cda
GitHub commit

commit 18eac8d547b4 (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/18eac8d547b4382bf830c621b20a35932dd1cfa5
GitHub advisoryMentions a patch (unverified)

AMQP 1.0 management exchange.declare skips alternate-exchange permission check · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-rg2g-289m-xhhw

Vendor Advisories for CVE-2026-67241(1)

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

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

Frequently asked(5)

What is CVE-2026-67241?
CVE-2026-67241 is a medium-severity vulnerability; its CVE record was published on September 25, 2026. RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, AMQP 1.0 management exchange.declare skips alternate-exchange permission check. pUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbitexchange:declare/7.…
When was the CVE record for CVE-2026-67241 published?
The CVE record for CVE-2026-67241 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-67241 actively exploited?
CVE-2026-67241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67241?
CVE-2026-67241 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-67241?
A fix for CVE-2026-67241 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67241 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-67241

Explore →

Is Your Infrastructure Affected by CVE-2026-67241?

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