CVE-2026-67234Low· 2.3▾ SunlitRabbitMQ 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 …
▾ Sunlit zone — Low / medium · no exploitation signal
impact 12.6 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-67237High· 7.5RabbitMQ is a messaging and streaming broker
CVE-2026-67236High· 8.2RabbitMQ is a messaging and streaming broker
CVE-2026-67222Medium· 5.9RabbitMQ is a messaging and streaming broker
CVE-2026-67230Medium· 6.3RabbitMQ is a messaging and streaming broker
CVE-2026-66078Low· 2.1RabbitMQ is a messaging and streaming broker
CVE-2026-66071Medium· 6.0RabbitMQ is a messaging and streaming broker