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)
do firstUpgrade to a fixed release: 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. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.
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
- affected>= 4.2.0 and < 4.2.8
- affected>= 4.3.0 and < 4.3.2
As published in the CVE Program record, and, for products that ship the affected component, in the advisory named beside them. 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.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- partial
Assessed by CISA 28 Sept 2026 (SSVC 2.0.3).
timeline
- 25 Sept 2026Published
- 26 Sept 2026Analysed by vulneraibility.com · 1 day later
- 28 Sept 2026CISA SSVC assessment: exploitation none · 2 days later
- 28 Sept 2026CVE record last updated · same day later
also known as
- Linkgithub.com /rabbitmq/rabbitmq-server/security/advisories/GHSA-88vh-gx85-p36m
- Linkgithub.com /rabbitmq/rabbitmq-server/commit/df9e7f4c0afd311a672705f020d301efad355745
- Linkgithub.com /rabbitmq/rabbitmq-server/commit/edf1fbc7217aaf736955d2e13c9534901a2e0778
- Linkgithub.com /rabbitmq/rabbitmq-server/releases/tag/v4.2.8
- Linkgithub.com /rabbitmq/rabbitmq-server/releases/tag/v4.3.2
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.