RabbitMQ rabbitmq-server是RabbitMQ组织的消息队列中间件。 rabbitmq-server 4.2.5之前版本存在跨站脚本漏洞,该漏洞源于RabbitMQ管理UI在Queues和Exchanges页面中将x-internal-purpose队列或交换参数渲染为HTML title属性时未正确转义,导致具有声明队列或交换权限的用户可以在其他用户浏览器中执行JavaScript。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| rabbitmq | rabbitmq-server | >= 4.2.0, < 4.2.5 |
affected |
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.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| rabbitmq | rabbitmq-server | >= 4.2.0, < 4.2.5 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-57219 | 8.7 HIGH | RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint |
| CVE-2026-57220 | 7.5 HIGH | RabbitMQ: Stream listener does not enforce configured frame-size limit during authenticati |
| CVE-2026-57216 | 6.8 MEDIUM | RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote gu |
| CVE-2026-57211 | 6.5 MEDIUM | RabbitMQ: UNC SSRF affecting the management UI on Windows |
| CVE-2026-57218 | RabbitMQ: AMQP 0-9-1 in combination with OAuth 2: consumer persistence can lead to post-re | |
| CVE-2026-57213 | RabbitMQ: Stored XSS federation management plugin via unsanitized consumer_tag rendering | |
| CVE-2026-57217 | RabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass | |
| CVE-2026-57212 | RabbitMQ management HTTP API accepts request bodies larger than configured max_http_body_s | |
| CVE-2026-57215 | RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injec | |
| CVE-2026-57221 | RabbitMQ: Passive queue/exchange declaration bypasses authorization checks, leaking queue |
No comments yet