RabbitMQ Node can log Basic Auth header from an HTTP request
RabbitMQ is a messaging and streaming broker. In versions 3.13.7 and prior, RabbitMQ is logging authorization headers in plaintext encoded in base64. When querying RabbitMQ api with HTTP/s with basic authentication it creates logs with all headers in request, including authorization headers which show base64 encoded username:password. This is easy to decode and afterwards could be used to obtain control to the system depending on credentials. This issue has been patched in version 4.0.8.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2025-50200
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 09:03 UTC · Revision 1
Source evidence
RabbitMQ Node can log Basic Auth header from an HTTP request
core-osv · Original sourcePublished 19 Jun 2025, 16:14 UTC
RabbitMQ is a messaging and streaming broker. In versions 3.13.7 and prior, RabbitMQ is logging authorization headers in plaintext encoded in base64. When querying RabbitMQ api with HTTP/s with basic authentication it creates logs with all headers in request, including authorization headers which show base64 encoded username:password. This is easy to decode and afterwards could be used to obtain control to the system depending on credentials. This issue has been patched in version 4.0.8.
osv:CVE-2025-50200
Complete source record
{
"id": "9ee4eac13bc1f93a23e99813bc059fd568f9dbd8c5b5082e2632e0dcbf2d2cf4",
"url": "https://osv.dev/vulnerability/CVE-2025-50200",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "RabbitMQ Node can log Basic Auth header from an HTTP request",
"summary": "RabbitMQ is a messaging and streaming broker. In versions 3.13.7 and prior, RabbitMQ is logging authorization headers in plaintext encoded in base64. When querying RabbitMQ api with HTTP/s with basic authentication it creates logs with all headers in request, including authorization headers which show base64 encoded username:password. This is easy to decode and afterwards could be used to obtain control to the system depending on credentials. This issue has been patched in version 4.0.8.",
"evidence": "osv:CVE-2025-50200",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2025-50200",
"aliases": [
"BIT-rabbitmq-2025-50200",
"CVE-2025-50200",
"GHSA-gh3x-4x42-fvq8"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/rabbitmq/rabbitmq-server",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "7a7eb55fa9d240247c9285cc421e98fb2d093e98"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "3.13.7"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"cpe": "cpe:2.3:a:broadcom:rabbitmq_server:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "4.0.8"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v4.0.7",
"v4.0.6",
"v4.0.5",
"v4.0.4",
"v4.0.3",
"v4.0.2",
"v4.0.1",
"v4.0.0",
"v4.0.0-rc.2",
"v4.0.0-rc.1",
"v4.0.0-beta.6",
"v4.0.0-beta.5",
"v4.0.0-beta.4",
"v4.0.0-beta.3",
"v4.0.0-beta.2",
"v4.0.0-beta.1",
"v0.0.0-beta.1",
"v3.13.0-rc.6",
"v3.13.0",
"v3.13.0-rc.5",
"v3.13.0-rc.4",
"v3.13.0-rc.3",
"v3.13.0-rc.2",
"v3.13.0-rc.1",
"v3.13.0-beta.6",
"v3.13.0-beta.5",
"v3.13.0-beta.4",
"v3.13.0-beta.3",
"v3.13.0-beta.2",
"v3.13.0-beta.1",
"v3.11.0-rc.2",
"v3.8.10",
"v3.8.0-rc.1",
"v3.8.0-beta.7",
"v3.8.0-beta.6",
"v3.8.0-beta.5",
"v3.8.0-beta.4",
"v3.8.0-beta.3",
"v3.8.0-beta.2",
"v3.8.0-beta.1",
"v3.7.0-rc.2",
"v3.7.0-rc.1",
"v3.7.0-beta.20",
"v3.7.0-beta.19",
"rabbitmq_v3_7_0_milestone18",
"rabbitmq_v3_7_0_milestone17",
"rabbitmq_v3_7_0_milestone16",
"rabbitmq_v3_7_0_milestone15",
"rabbitmq_v3_7_0_milestone14",
"rabbitmq_v3_7_0_milestone13",
"rabbitmq_v3_7_0_milestone12",
"rabbitmq_v3_7_0_milestone11",
"rabbitmq_v3_7_0_milestone10",
"rabbitmq_v3_7_0_milestone9",
"rabbitmq_v3_7_0_milestone8",
"rabbitmq_v3_7_0_milestone7",
"rabbitmq_v3_7_0_milestone5",
"rabbitmq_v3_7_0_milestone4",
"rabbitmq_v3_7_0_milestone3",
"rabbitmq_v3_7_0_milestone2",
"rabbitmq_v3_7_0_milestone1",
"rabbitmq_v3_6_0",
"rabbitmq_v3_6_0_rc3",
"rabbitmq_v3_6_0_rc2",
"rabbitmq_v3_6_0_rc1",
"rabbitmq_v3_6_0_milestone3",
"rabbitmq_v3_6_0_milestone2",
"rabbitmq_v3_6_0_milestone1",
"rabbitmq_v3_5_0",
"rabbitmq_v3_4_3",
"rabbitmq_v3_4_2",
"rabbitmq_v3_4_1",
"rabbitmq_v3_4_0",
"rabbitmq_v3_3_5",
"rabbitmq_v3_3_4",
"rabbitmq_v3_3_3",
"rabbitmq_v3_3_2",
"rabbitmq_v3_3_1",
"rabbitmq_v3_3_0",
"rabbitmq_v3_2_4",
"rabbitmq_v3_2_3",
"rabbitmq_v3_2_2",
"rabbitmq_v3_2_1",
"rabbitmq_v3_1_5",
"rabbitmq_v3_1_4",
"rabbitmq_v3_1_3",
"rabbitmq_v3_1_2",
"rabbitmq_v3_1_1",
"rabbitmq_v3_0_4",
"rabbitmq_v3_0_3",
"rabbitmq_v3_0_2",
"rabbitmq_v3_0_1",
"rabbitmq_v3_0_0",
"rabbitmq_v2_8_0",
"rabbitmq_v2_7_1",
"rabbitmq_v2_4_0",
"rabbitmq_v1_8_1",
"rabbitmq_v1_7_2",
"rabbitmq_v1_7_0",
"rabbitmq_v1_6_0",
"rabbitmq_v1_5_0",
"rabbitmq_v1_4_0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-50200.json"
}
}
],
"modified": "2026-10-28T02:30:50.355937598Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/50xxx/CVE-2025-50200.json",
"https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-gh3x-4x42-fvq8",
"https://nvd.nist.gov/vuln/detail/CVE-2025-50200"
],
"provider_metadata": {
"cwe_ids": [
"CWE-532"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/50xxx/CVE-2025-50200.json"
}
},
"related_cves": [
{
"value": "CVE-2025-50200",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 518835,
"published_at": "2025-06-19T16:14:24.919+00:00"
}