CVE-2026-67241

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.8Exploit: Elevated riskExposed 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
4.8
EG Score
4.8MEDIUMmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity48% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 29, 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 Patch Available

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 / EcosystemFixed in / 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 24× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 11:06 UTCEG score recompute
  2. 2026-10-04 11:06 UTCVendor advisory
  3. 2026-10-03 14:26 UTCEPSS rescore
  4. 2026-10-03 13:05 UTCEG score recompute
  5. 2026-10-03 13:05 UTCVendor advisory
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-02 15:03 UTCEG score recompute
  8. 2026-10-02 15:03 UTCVendor advisory
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-10-01 17:01 UTCVendor advisory
  11. 2026-09-30 18:48 UTCEG score recompute
  12. 2026-09-30 18:48 UTCVendor advisory
  13. 2026-09-30 15:03 UTCEPSS rescore
  14. 2026-09-29 20:31 UTCEG score recompute
  15. 2026-09-29 20:31 UTCVendor advisory
  16. 2026-09-29 19:38 UTCEG score recompute
  17. 2026-09-29 19:38 UTCVendor advisory
  18. 2026-09-29 12:46 UTCEG score recompute
  19. 2026-09-29 12:46 UTCVendor advisory
  20. 2026-09-28 14:44 UTCEG score recompute
  21. 2026-09-28 14:44 UTCVendor advisory
  22. 2026-09-28 13:52 UTCEPSS rescore
  23. 2026-09-28 11:45 UTCEG score recompute
  24. 2026-09-28 11:45 UTCVendor advisory
  25. 2026-09-27 13:48 UTCEPSS rescore
Show 6 more
  1. 2026-09-27 13:43 UTCEG score recompute
  2. 2026-09-27 13:43 UTCVendor advisory
  3. 2026-09-26 15:59 UTCEPSS rescore
  4. 2026-09-25 17:37 UTCEG score recompute
  5. 2026-09-25 16:24 UTCEG score recompute
  6. 2026-09-25 16:24 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67241?
CVE-2026-67241 is a medium vulnerability 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 CVE-2026-67241 disclosed?
CVE-2026-67241 was first published on September 25, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67241 actively exploited?
CVE-2026-67241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67241?
CVE-2026-67241 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
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

Explore the affected products and dependency analysis for 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.

Book a Demo →Browse All CVEs