Is CVE-2026-66068 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-66068 being exploited in the wild.

How severe is CVE-2026-66068?

Informational severity, published 23 September 2026.

Which products and versions are affected?

RabbitMQ before 3.13.15, before 4.0.20, before 4.1.11, before 4.2.6, before 4.3.0.

Is there a fix for CVE-2026-66068?

A patch was published on 2026-04-23: Fixed in RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-66068 attacked?

It is attacked with local access, in a hosted service.

Am I affected by CVE-2026-66068?

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.

CVE-2026-66068: RabbitMQ Shovel plaintext credentials in debug logs

CVE-2026-66068 · Severity: info · Published 2026-09-23

RabbitMQ is a message broker used by applications to queue and route messages reliably. When the Shovel plugin transfers messages between brokers using auto-delete configuration with DEBUG logging enabled, plaintext AMQP credentials embedded in URIs are written to broker logs. An attacker with access to log files could extract these credentials to compromise message routing and intercept sensitive communications.

Technologies: RabbitMQ. Vendors: RabbitMQ.

Quick answers

Is CVE-2026-66068 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-66068 being exploited in the wild.
How severe is CVE-2026-66068?: Informational severity, published 23 September 2026.
Which products and versions are affected?: RabbitMQ before 3.13.15, before 4.0.20, before 4.1.11, before 4.2.6, before 4.3.0.
Is there a fix for CVE-2026-66068?: A patch was published on 2026-04-23: Fixed in RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-66068 attacked?: It is attacked with local access, in a hosted service.
Am I affected by CVE-2026-66068?: 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 in the Shovel worker component which logs the entire shovel state map without redacting decrypted credentials. The affected code path is triggered when an autodelete shovel (src-delete-after configured) completes shutdown. The rabbit_shovel_worker lacks a format_status callback to redact sensitive fields before logging at DEBUG level. Attack requires DEBUG logging enabled (non-default), Shovel plugin enabled, URI-embedded credentials, and read access to broker logs.

Affected products

RabbitMQ RabbitMQ before 3.13.15, before 4.0.20, before 4.1.11, before 4.2.6, before 4.3.0

Timeline

2026-09-23: disclosed
2026-04-23: patched: Fixed in RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.