CVE-2026-67236: RabbitMQ insecure authentication cookie in management console

CVE-2026-67236 · Severity: info · Published 2026-09-25

RabbitMQ's management console stores login credentials in browser cookies without proper security protections. An attacker with access to the network, the browser, or through a cross-site scripting vulnerability can retrieve and decode the base64-encoded credentials to gain administrative access to the messaging broker.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67236 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67236 being exploited in the wild.
How severe is CVE-2026-67236?
Informational severity, published 25 September 2026.
Which products and versions are affected?
VMware RabbitMQ 4.2.0 to 4.2.7, 4.3.0 to 4.3.1.
Is there a fix for CVE-2026-67236?
A patch was published on 2026-09-25: Fixed in versions 4.2.8 and 4.3.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67236 attacked?
It is attacked over the network or with local access or from the adjacent network, in a hosted service.
Am I affected by CVE-2026-67236?
Check whether you run VMware RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The POST /login endpoint in RabbitMQ's management console sets an authentication cookie containing base64-encoded username:password pairs without HttpOnly, Secure, SameSite, or expiration attributes. Base64 encoding provides no encryption protection, allowing attackers with same-origin XSS, network eavesdropping capability, or local browser cookie store access to recover plaintext credentials. Fixes applied in 4.2.8 and 4.3.2 remove the insecure cookie.

Affected products

  • VMware RabbitMQ 4.2.0 to 4.2.7, 4.3.0 to 4.3.1

Timeline

  • 2026-09-25: disclosed
  • 2026-09-25: patched: Fixed in versions 4.2.8 and 4.3.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.