Skip to main content
← All vulnerabilities
CVE-2026-67406BIT-RABBITMQ-2026-67406GHSA-Q44F-9VC5-GRH7

RabbitMQ: Federation and Shovel Gen-Servers Lack format_status Callback — Plaintext Credentials Exposed in Crash Dumps and sys:get_status

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 4.3.3, 4.2.9, 4.1.14, 4.0.23
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.3.3, 4.2.9, 4.1.14, and 4.0.23, Shovel does not format state logged by the crash reporter and can leave unencrypted credentials in a crash dump file. the shovel worker genserver processes does not implement the formatstatus/2 callback. When these processes crash (e.g., due to network partitions, connection failures), the OTP SASL error handler writes the full process state , including plaintext AMQP passwords and URIs , to the error log. This is particularly severe for the shovel worker, which stores deobfuscated plaintext URIs (including amqp://user:password@host format) in its genserver state for the entire process Automatic Credential Exposure: Shovel worker crashes (common during network partitions) automatically write plaintext upstream/downstream passwords to error logs No Special Configuration Needed: Unlike DEBUG logging, SASL error reports are always active Broad. This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  3. Record last updated

Affected versions

  • rabbitmq rabbitmq-server

    From 4.3.0 · fixed in 4.3.3; From 4.2.0 · fixed in 4.2.9; From 4.1.0 · fixed in 4.1.14; From 4.0.0 · fixed in 4.0.23

  • rabbitmqBitnami

    From 4.0.0 · fixed in 4.0.23; From 4.1.0 · fixed in 4.1.14; From 4.2.0 · fixed in 4.2.9; From 4.3.0 · fixed in 4.3.3

References 3

GitHub · rabbitmq/rabbitmq-server