CVE-2026-67406: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in rabbitmq rabbitmq-server
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.
AI Analysis
Technical Summary
RabbitMQ's Shovel worker genserver processes lack implementation of the formatstatus/2 callback, leading to unformatted crash reports that include plaintext AMQP URIs and passwords in error logs. When these processes crash, the OTP SASL error handler logs the full process state, exposing sensitive credentials. This vulnerability affects multiple version branches from 4.0.0 up to but not including the fixed versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3. No special logging configuration is needed as SASL error reports are always active. The flaw is addressed by fixes in the specified versions.
Potential Impact
Sensitive AMQP credentials, including usernames and passwords in plaintext, can be exposed in error logs when the Shovel worker crashes. This exposure can lead to unauthorized access if logs are accessed by attackers or unauthorized personnel. The vulnerability is medium severity with a CVSS 4.6 score, reflecting network attack vector, low attack complexity, and partial attack requirements. There is no indication of active exploitation in the wild.
Mitigation Recommendations
Upgrade rabbitmq-server to one of the fixed versions: 4.3.3, 4.2.9, 4.1.14, or 4.0.23. This patch corrects the formatting of crash reports to prevent plaintext credential exposure. No additional configuration changes are required to mitigate this issue once patched.
CVE-2026-67406: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in rabbitmq rabbitmq-server
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.
CVSS v4.0
Score 4.6medium
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ's Shovel worker genserver processes lack implementation of the formatstatus/2 callback, leading to unformatted crash reports that include plaintext AMQP URIs and passwords in error logs. When these processes crash, the OTP SASL error handler logs the full process state, exposing sensitive credentials. This vulnerability affects multiple version branches from 4.0.0 up to but not including the fixed versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3. No special logging configuration is needed as SASL error reports are always active. The flaw is addressed by fixes in the specified versions.
Potential Impact
Sensitive AMQP credentials, including usernames and passwords in plaintext, can be exposed in error logs when the Shovel worker crashes. This exposure can lead to unauthorized access if logs are accessed by attackers or unauthorized personnel. The vulnerability is medium severity with a CVSS 4.6 score, reflecting network attack vector, low attack complexity, and partial attack requirements. There is no indication of active exploitation in the wild.
Mitigation Recommendations
Upgrade rabbitmq-server to one of the fixed versions: 4.3.3, 4.2.9, 4.1.14, or 4.0.23. This patch corrects the formatting of crash reports to prevent plaintext credential exposure. No additional configuration changes are required to mitigate this issue once patched.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-29T15:02:20.411Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a5d5f7a7c54106055640
Added to database: 09/25/2026, 16:48:21 UTC
Last enriched: 09/25/2026, 17:03:34 UTC
Last updated: 09/26/2026, 02:44:58 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.