RabbitMQ rabbitmq-server是RabbitMQ组织的消息队列中间件。 RabbitMQ rabbitmq-server 4.2.6之前版本存在授权问题漏洞,该漏洞源于授权问题,可能导致现有消费者在OAuth令牌过期或连接.secret刷新到减少范围后继续接收消息。
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| rabbitmq | rabbitmq-server | >= 4.2.0, < 4.2.6 |
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.6 | - |
|
| # | 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-57214 | RabbitMQ: Stored XSS in RabbitMQ management UI | |
| 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