Back to CVE records
Low 2.3Published Sep 25, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects rabbitmq-server. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
2.3 LOW (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-20
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Undergoing Analysis
Record last updated
Sep 25, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
rabbitmq rabbitmq-server
rabbitmq:server (from the name)
from 4.2.0, < 4.2.8; from 4.3.0, < 4.3.2
CNA record

References

  • x-refsource-confirm
  • x-refsource-misc
  • x-refsource-misc
  • x-refsource-misc
  • x-refsource-misc

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.