Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-67241)
Description
A vulnerability in RabbitMQ server versions from 4.2.0 up to but not including 4.2.9 and 4.3.3 allows users with configure permissions on an exchange to route unroutable messages to an alternate exchange without having write permissions on that alternate exchange. This occurs because the AMQP 1.0 management exchange.declare operation skips the alternate-exchange permission check. The issue is fixed in versions 4.2.9 and 4.3.3.
CVSS v4.0
Affected software
pkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra-legacy/xenialpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/bionicpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=esm-infra/focalpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=jammypkg:deb/ubuntu/rabbitmq-server?arch=source&distro=noblepkg:deb/ubuntu/rabbitmq-server?arch=source&distro=stonkingpkg:deb/ubuntu/rabbitmq-server?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ versions 4.2.0 through 4.2.8 and 4.3.0 through 4.3.2 contain a permission check bypass in the AMQP 1.0 management exchange.declare operation. Specifically, the code path for declaring exchanges in AMQP 1.0 does not enforce write permission checks on the alternate-exchange argument, unlike the AMQP 0-9-1 path which correctly enforces these checks. This allows a user with only configure permission on an exchange to route that exchange's unroutable messages into an alternate exchange for which they lack write permission. The vulnerability is addressed by adding the missing permission checks in RabbitMQ versions 4.2.9 and 4.3.3.
Potential Impact
An attacker with configure permissions on at least one exchange can misuse the alternate-exchange feature to route messages into an exchange they do not have write permission for. This could potentially allow unauthorized message routing manipulation within the messaging infrastructure, violating intended access controls. The vulnerability does not allow privilege escalation beyond the configure permission but bypasses intended write permission restrictions on alternate exchanges.
Mitigation Recommendations
This issue is fixed in RabbitMQ versions 4.2.9 and 4.3.3. Users should upgrade to at least these versions to remediate the vulnerability. No other mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-67241
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:Pro:18.04:LTS","Ubuntu:Pro:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.10","Ubuntu:26.04:LTS"]
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ad3f5a92cdf04f6566627e6
Added to database: 10/17/2026, 22:24:41 UTC
Last enriched: 10/17/2026, 23:57:12 UTC
Last updated: 10/17/2026, 23:57:12 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.