CVE-2026-67234

RabbitMQ: Non-RFC-conformant cookie name when clearing the auth-mechanism preference

State
Published
Severity
2.3 Low
Published
Sep 25, 2026
Updated
Sep 25, 2026
Reserved
Jul 28, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
4.02.3 LowCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NGitHub_M

Weaknesses

  • CWE-20 Improper Input Validation

Affected Products

ProductVersions
rabbitmq-serverrabbitmq
  • >= 4.2.0, < 4.2.8Affected
  • >= 4.3.0, < 4.3.2Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.