# CVE-2026-67241: RabbitMQ AMQP 1.0 alternate-exchange permission bypass

Source: https://junglewise.ai/threats/cve-2026-67241-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-2  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-25. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-67241 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker that applications use to reliably route messages between components. When configured to use the AMQP 1.0 protocol, RabbitMQ fails to check write permissions on alternate exchanges—backup destinations for unroutable messages. An attacker with permission to configure an exchange can redirect messages to an alternate exchange they don't have access to, potentially exposing message contents or causing data to be routed to an unauthorized destination.

Technologies: [RabbitMQ](https://junglewise.ai/threats/technologies/rabbitmq-rabbitmq). Vendors: [RabbitMQ](https://junglewise.ai/threats/vendors/rabbitmq).

## Quick answers

**Is CVE-2026-67241 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-67241 being exploited in the wild.

**How severe is CVE-2026-67241?** Informational severity, published 25 September 2026.

**Which products and versions are affected?** RabbitMQ 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.

**Is there a fix for CVE-2026-67241?** A patch was published on 2026-06-23: fix committed; patched versions 4.2.9 and 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-67241 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-67241?** 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 AMQP 1.0 management API's exchange.declare endpoint (PUT /exchanges/:name) skips the alternate-exchange permission check that is enforced for the AMQP 0-9-1 protocol path in rabbitchannel.erl:2540-2548. An attacker with only configure permission on exchange X can set an alternate exchange that they lack write permission for. This is a missing authorization check in the AMQP 1.0 management API implementation that was already correctly implemented for dead-letter exchanges on queues.

## Affected products

- RabbitMQ RabbitMQ 4.2.0 to 4.2.8, 4.3.0 to 4.3.2

## Timeline

- 2026-09-25: disclosed
- 2026-06-23: patched: fix committed; patched versions 4.2.9 and 4.3.3

## References

- [https://github.com/rabbitmq/rabbitmq-server/commit/18eac8d547b4382bf830c621b20a35932dd1cfa5](https://github.com/rabbitmq/rabbitmq-server/commit/18eac8d547b4382bf830c621b20a35932dd1cfa5)
- [https://github.com/rabbitmq/rabbitmq-server/commit/56005e7cebffc478ef397573de24aff1167e7cda](https://github.com/rabbitmq/rabbitmq-server/commit/56005e7cebffc478ef397573de24aff1167e7cda)

## Related threats

- [RabbitMQ OAuth privilege escalation via stale token tags](https://junglewise.ai/threats/cve-2026-67420-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ topic exchange denial of service via duplicate matchers](https://junglewise.ai/threats/cve-2026-67419-rabbitmq-is-a-messaging-and-streaming-broker-prior-to-4-3-5-an)
- [RabbitMQ Shovel denial of service via atom exhaustion](https://junglewise.ai/threats/cve-2026-67415-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-2)
- [RabbitMQ MQTT loopback user bypass via PROXY Protocol](https://junglewise.ai/threats/cve-2026-67411-rabbitmq-is-a-messaging-and-streaming-broker-from-3-13-0-until-3)
- [RabbitMQ OAuth2 client secret exposure via unauthenticated endpoint](https://junglewise.ai/threats/cve-2026-67410-rabbitmq-is-a-messaging-and-streaming-broker-from-4-2-0-until-4-3)