CVE-2025-50200: CWE-532: Insertion of Sensitive Information into Log File in rabbitmq rabbitmq-server
RabbitMQ versions 3.13.7 and earlier log HTTP authorization headers in plaintext base64 encoding, exposing encoded username and password in logs. This vulnerability allows sensitive credential information to be easily decoded from logs. The issue has been fixed in RabbitMQ version 4.0.8.
AI Analysis
Technical Summary
CVE-2025-50200 describes a vulnerability in RabbitMQ server (<=3.13.7) where authorization headers containing base64-encoded credentials are logged in plaintext. When clients use HTTP basic authentication to query the RabbitMQ API, all request headers including the Authorization header are logged. Since the Authorization header encodes username and password in base64, an attacker with access to logs can decode these credentials and potentially gain system control depending on the credentials obtained. This vulnerability is classified under CWE-532 (Insertion of Sensitive Information into Log File). The vulnerability has been patched in RabbitMQ version 4.0.8.
Potential Impact
Sensitive credentials (username and password) are exposed in logs in base64-encoded form, which can be trivially decoded. If an attacker gains access to these logs, they can retrieve valid credentials and potentially gain unauthorized access or control over the RabbitMQ system. The CVSS 4.0 score is 6.7 (medium severity), reflecting local attack vector with low attack complexity but requiring high privileges to exploit.
Mitigation Recommendations
Upgrade RabbitMQ to version 4.0.8 or later, where this logging behavior has been corrected. Until upgrading, restrict access to RabbitMQ logs to trusted personnel only to prevent credential leakage. No other vendor advisory mitigation instructions are provided.
CVE-2025-50200: CWE-532: Insertion of Sensitive Information into Log File in rabbitmq rabbitmq-server
Description
RabbitMQ versions 3.13.7 and earlier log HTTP authorization headers in plaintext base64 encoding, exposing encoded username and password in logs. This vulnerability allows sensitive credential information to be easily decoded from logs. The issue has been fixed in RabbitMQ version 4.0.8.
CVSS v4.0
Score 6.7medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-50200 describes a vulnerability in RabbitMQ server (<=3.13.7) where authorization headers containing base64-encoded credentials are logged in plaintext. When clients use HTTP basic authentication to query the RabbitMQ API, all request headers including the Authorization header are logged. Since the Authorization header encodes username and password in base64, an attacker with access to logs can decode these credentials and potentially gain system control depending on the credentials obtained. This vulnerability is classified under CWE-532 (Insertion of Sensitive Information into Log File). The vulnerability has been patched in RabbitMQ version 4.0.8.
Potential Impact
Sensitive credentials (username and password) are exposed in logs in base64-encoded form, which can be trivially decoded. If an attacker gains access to these logs, they can retrieve valid credentials and potentially gain unauthorized access or control over the RabbitMQ system. The CVSS 4.0 score is 6.7 (medium severity), reflecting local attack vector with low attack complexity but requiring high privileges to exploit.
Mitigation Recommendations
Upgrade RabbitMQ to version 4.0.8 or later, where this logging behavior has been corrected. Until upgrading, restrict access to RabbitMQ logs to trusted personnel only to prevent credential leakage. No other vendor advisory mitigation instructions are provided.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-06-13T19:17:51.728Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 68543b7133c7acc0460d50da
Added to database: 06/19/2025, 16:31:45 UTC
Last enriched: 09/08/2026, 13:21:10 UTC
Last updated: 09/10/2026, 19:36:50 UTC
Views: 333
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.
External Links
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.