RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, get_auth_mechanism/1 used term_to_binary/1 on the strict_auth_mechanism or preferred_auth_mechanism atom when clearing the corresponding cookie, producing a non-ASCII cookie name that violates RFC 6265 and can prevent the browser from deleting the preference. The issue is not directly exploitable for code execution or data exfiltration; its security relevance is limited to stale authentication-mechanism preferences persisting across logout and login cycles. This issue is fixed in versions 4.2.8 and 4.3.2.
CVE-2026-67234
LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence
This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (44th 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
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 2.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 2.3
- EG Score
- 2.3LOWmedium confidence
- EG Risk
- 15EG Risk 15/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 computedSeverity23% × 45%Exploitation1% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.6%
- EPSS %ILE
- 44th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). 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
References (5)
- security-advisories@githubhttps://github.com/rabbitmq/rabbitmq-server/commit/149cb59d618cefa83c6deb02dbbb1e8a7a2bc968
- security-advisories@githubhttps://github.com/rabbitmq/rabbitmq-server/commit/baac0aaf170efeb4f124ee36b8417274fa8dcc1a
- security-advisories@githubhttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8
- security-advisories@githubhttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2
- security-advisories@githubhttps://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q286-p3m9-j69f
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 13× 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.
- 2026-10-04 01:33 UTCEG score recompute
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-02 17:56 UTCEPSS rescore
- 2026-10-01 19:50 UTCEPSS rescore
- 2026-10-01 08:08 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescore
- 2026-09-28 14:02 UTCEG score recompute
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 17:40 UTCEG score recompute
- 2026-09-25 16:24 UTCEG score recompute
- 2026-09-25 16:24 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-67234?
CVE-2026-67234 is a low vulnerability published on September 25, 2026. RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, getauthmechanism/1 used termtobinary/1 on the strictauthmechanism or preferredauthmechanism atom when clearing the corresponding cookie, producing a non-ASCII cookie name that violates RFC 6265 and can prevent the…
When was CVE-2026-67234 disclosed?
CVE-2026-67234 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-67234 actively exploited?
CVE-2026-67234 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-67234?
CVE-2026-67234 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-67234?
A fix for CVE-2026-67234 is available — its CVE record says: "This issue is fixed in versions 4.2.8 and 4.3.2."
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-67234
Is Your Infrastructure Affected by CVE-2026-67234?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.