CVE-2026-66068 json
RabbitMQ: Shovel DEBUG log of full state exposes decrypted URIs
published 2026-09-23 46 d ago modified 2026-10-20 19 d ago also BIT-rabbitmq-2026-66068 , EUVD-2026-85651 , GHSA-9wm4-9m6g-w38x
- cvss
- 4.4
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0, ?LOG_DEBUG("shutting down Shovel '~ts', ... Shovel state: ~tp", [Name, State]) formats the entire state map. The 'uris' field holds plaintext URIs after credentials_obfuscation:decrypt (called in rabbit_shovel_util:deobfuscated_uris/2). No format_status/1,2 callback exists in rabbit_shovel_worker to redact it. Triggered when an autodelete shovel (src-delete-after = N) completes. With DEBUG logging enabled, autodelete-shovel completion writes the full shovel state map , including decrypted amqp://user:password@host/ URIs , to the broker log file. Preconditions include Shovel plugin enabled with URI-embedded credentials DEBUG log level (non-default) Autodelete shovel configuration Attacker has log read access. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
Patch / fix
- bitnami rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
- vmware rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
- pivotal_software rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6
- rabbitmq-server Debian 14 4.3.0-2
debian advisories DEBIAN-CVE-2026-66068
- rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1
red hat advisories RHSA-2026:67552
- rabbitmq-server Azure Linux 3.0 3.13.7-10
azure linux advisories AZL-105771
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-66068 updated cvss 4.1
rabbitmq: RabbitMQ: Information disclosure of decrypted Shovel URIs in debug logs
-
Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1affected: no fix planned “Will not fix”
-
Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1fixed: vendor fix RHSA-2026:67552
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 45 d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.6 | CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 4.0 | 5.6 | CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | rabbitmq | >=3.13.0, <3.13.15 >=4.0.0, <4.0.20 >=4.1.0, <4.1.11 >=4.2.0, <4.2.6 |
3.13.15 4.0.20 4.1.11 4.2.6 |
Affected products
- rabbitmq rabbitmq-server
Classification
- Weakness
-
- CWE-532 Insertion of Sensitive Information into Log File
References
-
github.com
/rabbitmq/rabbitmq-server/security/advisories/GHSA-9wm4-9m6g-w38x
vendor-advisory, advisory
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.2.6
release-notes, article
-
github.com
/rabbitmq/rabbitmq-server/releases/tag/v4.3.0
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-66068
web
Sources
- CVE List CVE-2026-66068
- NVD CVE-2026-66068
- OSV BIT-rabbitmq-2026-66068
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.