Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67234)
Description
A vulnerability in RabbitMQ server versions from 4.2.0 up to but not including 4.2.8 and version 4.3.2 causes non-ASCII cookie names due to improper handling of authentication mechanism atoms. This violates RFC 6265 and can prevent browsers from deleting stale authentication-mechanism cookies, causing preferences to persist across logout and login cycles. The issue does not allow code execution or data exfiltration and is fixed in versions 4.2.8 and 4.3.2.
CVSS v4.0
Affected software
pkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/bionicpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/focalpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=jammypkg:deb/ubuntu/rabbitmq-server?arch=source&distro=noblepkg:deb/ubuntu/rabbitmq-server?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ server versions 4.2.0 through 4.2.7 and 4.3.2 have a flaw in the get_auth_mechanism/1 function where term_to_binary/1 is applied to strict_auth_mechanism or preferred_auth_mechanism atoms, resulting in non-ASCII cookie names. This violates RFC 6265 cookie specifications and can cause browsers to fail to delete authentication-mechanism cookies, leading to stale preferences persisting after logout and login. The vulnerability does not enable code execution or data exfiltration. The issue is resolved in RabbitMQ versions 4.2.8 and 4.3.2.
Potential Impact
The vulnerability's impact is limited to the persistence of stale authentication-mechanism preferences across logout and login cycles due to non-deleted cookies. There is no direct risk of code execution, data exfiltration, or other security breaches.
Mitigation Recommendations
This issue is fixed in RabbitMQ versions 4.2.8 and 4.3.2. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigation actions are necessary.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-67234
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.04:LTS"]
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad3f5aa2cdf04f6566627ef
Added to database: 10/17/2026, 22:24:42 UTC
Last enriched: 10/18/2026, 00:01:46 UTC
Last updated: 10/18/2026, 00:01:46 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.