RabbitMQ: Non-RFC-conformant cookie name when clearing the auth-mechanism preference (CVE-2026-67234) | HOL Guard CVE

Low · CVSS 2.3CVE-2026-67234

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

Answer in brief

CVE-2026-67234 records a Low severity (CVSS 2.3) vulnerability in RabbitMQ: Non-RFC-conformant cookie name when clearing the auth-mechanism preference. The current sources do not mark it as known exploited. The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Low · CVSS 2.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 2.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps rabbitmq/rabbitmq-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
rabbitmq/rabbitmq-servergeneric	>=4.2.0 <4.2.8 \|\| >=4.3.0 <4.3.2	4.2.8, 4.3.2

Recommended response

Check inventory. Check lockfiles and deployed manifests for rabbitmq/rabbitmq-server.
Review the reported fix. Update rabbitmq/rabbitmq-server to 4.2.8 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.