2.3Low

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

rabbitmq rabbitmq-server Published: (1 month ago)

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.

Weakness (CWE): CWE-20

Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.

Affected products and versions

VendorProductVersions
broadcom rabbitmq server 4.2.0 – < 4.2.8
rabbitmq rabbitmq-server >= 4.2.0, < 4.2.8, >= 4.3.0, < 4.3.2

References and patches

CPE matches (NVD) (2)

  • cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* ≥ 4.2.0 < 4.2.8
  • cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:* ≥ 4.3.0 < 4.3.2