CVEvulnerability

CVE-2026-67236

8.2 HIGH Published 2026-09-25 Modified 2026-10-15 Official page ↗
Status
Analyzed
Published
2026-09-25
Last modified
2026-10-15
Assigner
[email protected]
CVSS 4.0 ([email protected])
8.2 HIGH — CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 ([email protected])
6.5 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-312

Description

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 configurations

• broadcom rabbitmq server (>= 4.2.0 < 4.2.8) • broadcom rabbitmq server (>= 4.3.0 < 4.3.2)

Related

Weakness · CWE (1)

  • CWE-312 Cleartext Storage of Sensitive Information weakness

References