CVE-2026-67236

published 25 Sep 2026 · updated 28 Sep 2026

RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login

8.2HighCVSS 8.2EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=4.2.0 <4.2.8, >=4.3.0 <4.3.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67236 severity on Zeptric[![CVE-2026-67236](https://zeptric.io/badge/cve/CVE-2026-67236.svg)](https://zeptric.io/cve/CVE-2026-67236)