| Name | 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. |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| rabbitmq-server (PTS) | bookworm, bookworm (security) | 3.10.8-1.1+deb12u1 | fixed |
| trixie | 4.0.5-6+deb13u2 | fixed |
| forky | 4.3.2-4 | vulnerable |
| sid | 4.3.2-5 | vulnerable |
The information below is based on the following data on fixed versions.
Notes
[trixie] - rabbitmq-server <not-affected> (Vulnerable code not present, only affects 4.2.x and later)
[bookworm] - rabbitmq-server <not-affected> (Vulnerable code not present, only affects 4.2.x and later)
https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q286-p3m9-j69f