Medium severity4.3NVD Advisory· Published Sep 25, 2026· Updated Oct 20, 2026
CVE-2026-67234
CVE-2026-67234
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
3- cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*Range: >=4.2.0,<4.2.8
- Range: 4.2.0 - 4.2.8, 4.3.2
Patches
Vulnerability mechanics
References
5- github.com/rabbitmq/rabbitmq-server/commit/149cb59d618cefa83c6deb02dbbb1e8a7a2bc968nvdPatch
- github.com/rabbitmq/rabbitmq-server/commit/baac0aaf170efeb4f124ee36b8417274fa8dcc1anvdPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8nvdRelease NotesPatch
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2nvdRelease NotesPatch
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q286-p3m9-j69fnvdVendor Advisory
News mentions
1- RabbitMQ: 25 Vulnerabilities Disclosed Together, Highlighting Auth, UI, and DoS RisksVypr Intelligence · Sep 25, 2026