CVE-2026-67236
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, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding rather than encryption, an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials; older browsers that treated an absent SameSite attribute as None also sent the cookie cross-site. 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/df9e7f4c0afd311a672705f020d301efad355745
- github.com/rabbitmq/rabbitmq-server/commit/edf1fbc7217aaf736955d2e13c9534901a2e0778
- 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-88vh-gx85-p36m
- nvd.nist.gov/vuln/detail/CVE-2026-67236
- cve.org/CVERecord?id=CVE-2026-67236
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.