CVE-2026-67234

Medium

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.

SeverityMedium
CVSS4.3
Exploit probability—
ProductBroadcom Rabbitmq Server
PublishedSep 25, 2026
First seenSep 25, 2026

How to fix

Update
  • broadcom rabbitmq_server4.2.8, 4.3.2 or later

Affected products

ProductAffected versionsFixed in
broadcom rabbitmq_server4.2.0 ≤ v < 4.2.8, 4.3.0 ≤ v < 4.3.24.2.8, 4.3.2

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.