Rabbitmq server: RabbitMQ is a messaging and streaming broker. (CVE-2026-61837)
Description
CVE-2026-61837 is a vulnerability in RabbitMQ server versions prior to 4.3.3, 4.2.9, 4.1.14, and 4.0.23 where the AMQP 1.0 management GET /bindings endpoint exposes the full binding topology to any authenticated AMQP user without proper permission checks. This allows any authenticated AMQP 1.0 client, even without management or administrative privileges, to enumerate the complete routing topology of the virtual host they can access.
CVSS v3.1
Score 5.3medium
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 server versions from 4.0.0 up to but not including 4.3.3, 4.2.9, 4.1.14, and 4.0.23 have a vulnerability in the AMQP 1.0 HTTP-over-AMQP management endpoint GET /bindings. This endpoint returns the full binding topology (source exchanges, destination queues/exchanges, routing keys, and binding arguments) of the caller's virtual host without performing resource-level permission checks. Unlike other management operations that enforce access control, this GET handler ignores the authenticated user's permissions, allowing any authenticated AMQP 1.0 client to enumerate sensitive routing information. The issue is fixed in RabbitMQ versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23.
Potential Impact
The vulnerability allows a non-management AMQP 1.0 authenticated user to enumerate the complete routing topology of any virtual host they can connect to. This results in a confidentiality impact by exposing sensitive internal messaging infrastructure details, which could aid an attacker in further reconnaissance or targeted attacks. There is no direct impact on integrity or availability reported.
Mitigation Recommendations
This vulnerability is fixed in RabbitMQ versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23. Users should upgrade to one of these fixed versions to remediate the issue. No other mitigation or temporary workaround is indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-61837
- 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
- 3.1
- State
- PUBLISHED
Threat ID: 6ad3f5cd2cdf04f65666293c
Added to database: 10/17/2026, 22:25:17 UTC
Last enriched: 10/18/2026, 00:23:56 UTC
Last updated: 10/18/2026, 00:23:56 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.