UBUNTU-CVE-2026-57215
RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6 contain a vulnerability where foreign bindings to amq.rabbitmq.reply-to destinations are allowed due to missing deletion checks for volatile direct-reply-to queues. This results in persistent route entries after unbind operations. The issue is fixed in the specified later versions.
AI Analysis
Technical Summary
RabbitMQ messaging broker versions before 3.13.15, 4.0.20, 4.1.11, and 4.2.6 allow foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues are accepted at bind and route time but are not properly checked during deletion by the Khepri-backed mechanism. This causes persistent route entries to remain after unbind operations. The vulnerability is resolved in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
The vulnerability allows persistent route entries to remain after unbind operations, which could lead to unintended message routing behavior within RabbitMQ. No direct exploitation or known exploits in the wild are reported. The impact is limited to potential message routing inconsistencies due to leftover bindings.
Mitigation Recommendations
A fix is available in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
UBUNTU-CVE-2026-57215
Description
RabbitMQ versions prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6 contain a vulnerability where foreign bindings to amq.rabbitmq.reply-to destinations are allowed due to missing deletion checks for volatile direct-reply-to queues. This results in persistent route entries after unbind operations. The issue is fixed in the specified later versions.
CVSS v4.0
Affected software
pkg:deb/ubuntu/[email protected]+esm2?arch=source&distro=esm-infra/xenialpkg:deb/ubuntu/[email protected]?arch=source&distro=bionicpkg:deb/ubuntu/[email protected]?arch=source&distro=focalpkg:deb/ubuntu/[email protected]?arch=source&distro=jammypkg:deb/ubuntu/[email protected]?arch=source&distro=noblepkg:deb/ubuntu/[email protected]?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 messaging broker versions before 3.13.15, 4.0.20, 4.1.11, and 4.2.6 allow foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues are accepted at bind and route time but are not properly checked during deletion by the Khepri-backed mechanism. This causes persistent route entries to remain after unbind operations. The vulnerability is resolved in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
Potential Impact
The vulnerability allows persistent route entries to remain after unbind operations, which could lead to unintended message routing behavior within RabbitMQ. No direct exploitation or known exploits in the wild are reported. The impact is limited to potential message routing inconsistencies due to leftover bindings.
Mitigation Recommendations
A fix is available in RabbitMQ versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-57215
- Osv Schema Version
- 1.7.0
- Aliases
- []
- Ecosystems
- ["Ubuntu:Pro:16.04:LTS","Ubuntu:18.04:LTS","Ubuntu:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.04:LTS"]
- Database Specific Severity
- null
- Cvss Version
- 4.0
Threat ID: 6a58b46968715ace43d7984d
Added to database: 07/16/2026, 10:37:29 UTC
Last enriched: 07/16/2026, 11:41:57 UTC
Last updated: 07/31/2026, 19:24:50 UTC
Views: 4
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.