CVE-2026-67227

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th 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 week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1, Atom exhaustion: toatom on global-parameter :name. resourceexists/2 (and the PUT/DELETE handlers) call rabbitdatacoercion:toatom/1 on the :name URL path segment. toatom/1 uses binarytoatom/2 (unsafe). The endpoint requires policymaker (not management, but below A user with the policymaker tag can crash the node by exhausting the atom table via repeated requests to /api/global-parameters/:name with unique :name Management plugin enabled policymaker tag ~1M HTTP. This issue is fixed in versions 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack 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). 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 28, 2026

Advisory Details (5)

Auto-updated Sep 25, 2026
Patch available. Sources: github_release, github, github_commit.
github_release Patch Available

RabbitMQ 4.3.1

Patch available: rabbitmq/rabbitmq-server v4.3.1

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.1
github_release Patch Available

RabbitMQ 4.2.7

Patch available: rabbitmq/rabbitmq-server v4.2.7

https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7
github_commit

commit fc591e7ee27a (rabbitmq/rabbitmq-server)

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

https://github.com/rabbitmq/rabbitmq-server/commit/fc591e7ee27a29657ca960930acefd3e4217e007
github_commit

commit 8fbe6d811242 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 8fbe6d811242 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/8fbe6d8112427e85fb9a9206b3eb6e9a3ddd3e39
github Patch Available

Atom exhaustion: to_atom on global-parameter :name · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q7x8-97rh-cr24

Vendor Advisories for CVE-2026-67227(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 23× 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 14:23 UTCVendor advisory
  2. 2026-10-03 14:30 UTCEG score recompute
  3. 2026-10-03 14:30 UTCVendor advisory
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-02 17:56 UTCEPSS rescore
  6. 2026-10-02 14:35 UTCEG score recompute
  7. 2026-10-02 14:35 UTCVendor advisory
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-10-01 14:30 UTCEG score recompute
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-30 14:37 UTCEG score recompute
  12. 2026-09-29 14:37 UTCEG score recompute
  13. 2026-09-28 14:44 UTCEG score recompute
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-27 18:29 UTCEG score recompute
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-26 18:36 UTCEG score recompute
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-25 18:39 UTCEG score recompute
  20. 2026-09-25 17:58 UTCEG score recompute
  21. 2026-09-25 17:33 UTCEG score recompute
  22. 2026-09-25 16:39 UTCEG score recompute
  23. 2026-09-25 16:39 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67227?
CVE-2026-67227 is a medium vulnerability published on September 25, 2026. RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.0.22 and 4.1.14 and 4.2.7 and 4.3.1, Atom exhaustion: toatom on global-parameter :name. resourceexists/2 (and the PUT/DELETE handlers) call rabbitdatacoercion:toatom/1 on the :name URL path segment. toatom/1 uses binarytoatom/2…
When was CVE-2026-67227 disclosed?
CVE-2026-67227 was first published on September 25, 2026, with the most recent update on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67227 actively exploited?
CVE-2026-67227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67227?
CVE-2026-67227 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67227?
A fix for CVE-2026-67227 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67227 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-67227

Explore →

Is Your Infrastructure Affected by CVE-2026-67227?

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

Book a Demo →Browse All CVEs