Quick answers
- Is CVE-2026-67406 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67406 being exploited in the wild.
- How severe is CVE-2026-67406?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- RabbitMQ 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.
- Is there a fix for CVE-2026-67406?
- A patch was published on 2026-07-20: Fixed in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67406 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-67406?
- Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists because Shovel worker genserver processes do not implement the formatstatus/2 callback, allowing OTP's SASL error handler to log unfiltered process state containing plaintext deobfuscated URIs and passwords. Shovel stores credentials in plaintext in process state throughout the worker's lifetime, and worker crashes—common during network partitions or connection failures—trigger automatic credential exposure to error logs. The fix implements proper state formatting to redact sensitive data from crash reports.
Affected products
- RabbitMQ RabbitMQ 4.0.0 to 4.0.22, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2
Timeline
- 2026-09-25: disclosed: Vulnerability published
- 2026-07-20: patched: Fixed in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3