Skip to main content
VulnerabilityPublished Updated

CVE-2026-67236: rabbitmq-server · Cleartext Storage of Sensitive Information

Affects rabbitmq-serverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 4.3.2 or 4.2.8 soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 5% 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:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
rabbitmqrabbitmq-serverAffected
  • >=4.3.0 <4.3.2
Fixed in
  • 4.3.2
rabbitmqrabbitmq-serverAffected
  • >=4.2.0 <4.2.8
Fixed in
  • 4.2.8
GitHubrabbitmq/rabbitmq-serverpkg:github/rabbitmq/rabbitmq-serverOther threatsAffected
  • >=4.2.0 <4.2.8
  • >=4.3.0 <4.3.2
Fixed in
  • 4.2.8
  • 4.3.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in RabbitMQ versions 4.2.8 and 4.3.2. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.8 and 4.3.2, a successful POST /login caused is_authorized/2 to set an auth cookie containing base64-encoded username:password credentials without HttpOnly, Secure, SameSite, or expiration protections. Because base64 is encoding rather than encryption, an attacker with same-origin cross-site scripting, an HTTP-readable network position, or local access to the browser cookie store could recover the actual login credentials; older browsers that treated an absent SameSite attribute as None also sent the cookie cross-site. This issue is fixed in versions 4.2.8 and 4.3.2.

References

Community reviews

Loading reviews…