RabbitMQ is widely used enterprise messaging infrastructure; credential leak enables account compromise and lateral movement across organizations.
CVE-2026-67236
RabbitMQ auth cookie leaks base64 creds on POST /login (fixed in 4.2.8/4.3.2)
Is CVE-2026-67236 being exploited?
Not confirmed. CVE-2026-67236 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-67236?
CVE-2026-67236 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67236?
Yes. A fix has been recorded for CVE-2026-67236. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67236 affect?
CVE-2026-67236 affects RabbitMQ Server 4.2.0–4.2.7, RabbitMQ Server 4.3.0–4.3.1, Fixed in 4.2.8 and 4.3.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67236?
Upgrade to 4.2.8 or 4.3.2; rotate credentials and invalidate session cookies.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can extract plaintext user:pass from auth cookie via XSS, network sniffing, or local cookie access, enabling account compromise and lateral movement.
Patch when possible
- affected>= 4.2.0 and < 4.2.8
- affected>= 4.3.0 and < 4.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.