CVE-2026-67221: RabbitMQ: AMQP 1.0 shovel status exposes plaintext URI passwords

Published Sep 23, 2026
·
Updated

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, The AMQP 0-9-1 shovel calls amqpuri:removecredentials before storing its connection URI, but the AMQP 1.0 shovel stores the raw URI including the password. The stored URI is visible via GET /api/shovels and via rabbitmqctl shovelstatus. Preconditions include The Shovel plugin must be in use with AMQP 1.0 shovels configured using URI-embedded credentials. Reading the exposed status requires the monitoring tag.. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

Affected Software

1 affected component
RabbitMQ RabbitMQ<3.13.15, <4.0.20, <4.1.11, <4.2.6, <4.3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 3.13.15
  2. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.0.20
  3. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.1.11
  4. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.2.6
  5. Upgrade

    Upgrade RabbitMQ to a version that resolves this vulnerability.

    Fixed in 4.3.0

Event History

Sep 23, 2026
CVE Published
via MITRE·08:48 PM
Data Sourced
via MITRE·08:48 PM
DescriptionWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to credential disclosure?

Exposure requires the Shovel plugin to be in use and an AMQP 1.0 shovel to be configured with credentials embedded in its connection URI. AMQP 0-9-1 shovels remove credentials before storing the URI and are not the affected path described here.

2

What access does an attacker need to retrieve the password?

The attacker needs access to shovel status and the monitoring tag. The affected stored URI can be viewed through GET /api/shovels or the rabbitmqctl shovel_status command.

3

What should be done if an affected instance cannot be upgraded immediately?

Avoid configuring AMQP 1.0 shovels with URI-embedded credentials and restrict access to users with the monitoring tag. Credentials previously embedded in affected shovel URIs should be treated as exposed and rotated.

4

Which versions contain the fix?

The issue is fixed in RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203