CVE-2026-67234: rabbitmq-server · Improper Input Validation
Affects rabbitmq-serverSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 4.3.2 or 4.2.8 when convenient.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.3.2, 4.2.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade rabbitmq-server and rabbitmq/rabbitmq-server to 4.3.2 or 4.2.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
| rabbitmqrabbitmq-server | Affected
| Fixed in
|
GitHubrabbitmq/rabbitmq-serverpkg:github/rabbitmq/rabbitmq-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This issue is fixed in rabbitmq-server versions 4.2.8 and 4.3.2. Users should upgrade to these versions or later to resolve the vulnerability. No other mitigation is necessary as the issue does not pose a direct security risk beyond stale cookie persistence.
Description
CVE-2026-67234 is an improper input validation vulnerability in rabbitmq-server versions 4.2.0 through 4.2.7 and 4.3.0 through 4.3.1. The issue arises from the use of term_to_binary/1 on certain atoms to clear cookies, resulting in non-ASCII cookie names that violate RFC 6265. This can cause browsers to fail to delete authentication-mechanism preference cookies, leading to stale preferences persisting across logout and login cycles. The vulnerability does not allow code execution or data exfiltration. It is fixed in versions 4.2.8 and 4.3.2.
References
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q286-p3m9-j69f (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/commit/149cb59d618cefa83c6deb02dbbb1e8a7a2bc968 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/commit/baac0aaf170efeb4f124ee36b8417274fa8dcc1a (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.8 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.2 (opens in a new tab)