CVE-2026-67234
RabbitMQ is a messaging and streaming broker. From 4.2.0 until …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/rabbitmq/rabbitmq-server/commit/149cb59d618cefa83c6deb02dbbb1e8a7a2bc968
- github.com/rabbitmq/rabbitmq-server/commit/baac0aaf170efeb4f124ee36b8417274fa8dcc1a
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q286-p3m9-j69f
- nvd.nist.gov/vuln/detail/CVE-2026-67234
- cve.org/CVERecord?id=CVE-2026-67234
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.