CVE-2026-67234
RabbitMQ: Non-RFC-conformant cookie name when clearing the auth-mechanism preference
CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th
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.
| CWE | CWE-20 |
| Vendor | rabbitmq |
| Product | rabbitmq-server |
| Published | Sep 25, 2026 |
Stay Ahead of the Next One
Get instant alerts for rabbitmq rabbitmq-server
Be the first to know when new unknown vulnerabilities affecting rabbitmq rabbitmq-server are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
Affected Versions
rabbitmq / rabbitmq-server
>= 4.2.0, < 4.2.8 >= 4.3.0, < 4.3.2
References
github.com: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q286-p3m9-j69f github.com: https://github.com/rabbitmq/rabbitmq-server/commit/149cb59d618cefa83c6deb02dbbb1e8a7a2bc968 github.com: https://github.com/rabbitmq/rabbitmq-server/commit/baac0aaf170efeb4f124ee36b8417274fa8dcc1a github.com: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8 github.com: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2