Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-61837— RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks

Quick assessment

Affected
rabbitmq rabbitmq-server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

RabbitMQ 是一个消息和流式代理服务器。在版本 4.0.0 至 4.3.2、4.3.3 之前的 4.2.9、4.1.14 和 4.0.23 中，AMQP 1.0 的管理端点 GET /bindings 会向任何经过身份验证的 AMQP 用户暴露完整的绑定拓扑结构，且未进行资源/管理权限检查。 具体而言，AMQP 1.0 的 HTTP-over-AMQP 管理端点 GET /bindings（由 rabbitamqpmanagement 处理器处理）会枚举调用者所在虚拟主机中任意源交换机与目标队列/交换机之间的

CVSS 6.3 · Medium EPSS 0.25% · P14
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-61837

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
RabbitMQ: AMQP 1.0 management `GET /bindings` exposes full binding topology to any authenticated AMQP user without resource/management permission checks
Source: CVE Program / CVE List V5
Vulnerability Description
RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.3.3, 4.2.9, 4.1.14, and 4.0.23, AMQP 1.0 management GET /bindings exposes full binding topology to any authenticated AMQP user without resource/management permission checks. the AMQP 1.0 HTTP-over-AMQP management endpoint GET /bindings (the rabbitamqpmanagement handler) enumerates bindings between an arbitrary source exchange and destination queue/exchange in the caller's virtual host without performing any resource-level permission check. Unlike every sibling operation in the same module (which call checkresourceaccess / bindingchecks), the GET handler ignores the authenticated User and returns the binding list unchanged. As a result, any authenticated AMQP 1.0 client that can open a management link pair , including users with no management/monitoring/policymaker/administrator tag , can enumerate the complete binding topology (source exchanges, destination queues/exchanges, routing keys, and binding arguments) of the virtual host they can access. The equivalent HTTP management API (GET /api/bindings) Confidentiality impact: a non-management AMQP 1.0 user can enumerate the complete routing topology of any virtual host it can connect to , every (source exchange, destination queue/exchange, routing key, binding arguments) This issue is fixed in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
rabbitmq rabbitmq-server >= 4.3.0, < 4.3.3 -

II. Public POCs for CVE-2026-61837

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-61837

请登录查看更多情报信息。

Other References for CVE-2026-61837 (5)

Same Patch Batch · rabbitmq · 2026-09-25 · 28 CVEs total

CVE-2026-67410 8.2 HIGH RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint
CVE-2026-67236 8.2 HIGH RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /
CVE-2026-67409 8.2 HIGH RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Au
CVE-2026-67239 7.6 HIGH RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI
CVE-2026-67237 7.5 HIGH RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint
CVE-2026-67419 7.1 HIGH RabbitMQ: Consecutive topic wildcards cause combinatorial routing work
CVE-2026-67408 7.1 HIGH RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node
CVE-2026-67226 6.9 MEDIUM RabbitMQ: Admin-only atom exhaustion: PUT /api/users tags list
CVE-2026-67225 6.3 MEDIUM RabbitMQ: Stream-protocol frame length never validated against frame_max
CVE-2026-67242 6.3 MEDIUM RabbitMQ: OAuth2 is_integer(Exp) guard skips token-expiry checks for float exp
CVE-2026-67230 6.3 MEDIUM RabbitMQ: Web-STOMP unbounded pre-auth accumulation
CVE-2026-67223 6.3 MEDIUM RabbitMQ: LDAP DN injection via unescaped substitution
CVE-2026-66071 6.0 MEDIUM RabbitMQ: Atom exhaustion: OAuth2 JWT tag: scope values
CVE-2026-67411 6.0 MEDIUM RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass
CVE-2026-66073 6.0 MEDIUM RabbitMQ: Atom table exhaustion via management API node field
CVE-2026-67412 6.0 MEDIUM RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message acces
CVE-2026-67413 6.0 MEDIUM RabbitMQ: Authenticated RabbitMQ JMS Topic Selector Users Can Consume Broker CPU with an U
CVE-2026-67415 5.9 MEDIUM RabbitMQ: Shovel Management Atom Exhaustion Allows Persistent Broker-Wide Denial of Servic
CVE-2026-67222 5.9 MEDIUM RabbitMQ: list_to_atom on auth_mechanism URI tokens in amqp_client
CVE-2026-67227 5.9 MEDIUM RabbitMQ: Atom exhaustion: to_atom on global-parameter :name

Showing top 20 of 28 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

Same product: rabbitmq-server
Same vendor: rabbitmq
Same weakness: CWE-285

V. Comments for CVE-2026-61837

No comments yet

Leave a comment