Broadcom RabbitMQ Server

RabbitMQ: UNC SSRF affecting the management UI on Windows

RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks

An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12, and 1.7.x before 1.7.7. MQTT (MQ Telemetry Transport) connection authentication with a username/password pair succeeds if an existing username is provided but the password is omitted from the connection request. Connections that use TLS with a client-provided certificate are not affected.

RabbitMQ: Reflected XSS via the OAuth bootstrap JS endpoint

RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch

RabbitMQ: Trust-store whitelist by Issuer+Serial only

RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom

RabbitMQ: CORS * reflects Origin with Allow-Credentials

RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations

RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS

RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint

RabbitMQ: Web-MQTT decompression bomb

RabbitMQ: Pre-auth AMQP 1.0 array32 zero-width element DoS

RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login

RabbitMQ MQTT Topic Permission Authorization Bypass

RabbitMQ: CSWSH on Web-STOMP / Web-MQTT (no Origin validation)

RabbitMQ installers on Windows prior to version 3.8.16 do not harden plugin directory permissions, potentially allowing attackers with sufficient local filesystem permissions to add arbitrary plugins.

An issue was discovered in these Pivotal RabbitMQ versions: all 3.4.x versions, all 3.5.x versions, and 3.6.x versions prior to 3.6.9; and these RabbitMQ for PCF versions: all 1.5.x versions, 1.6.x versions prior to 1.6.18, and 1.7.x versions prior to 1.7.15. RabbitMQ management UI stores signed-in user credentials in a browser's local storage without expiration, making it possible to retrieve them using a chained attack.

RabbitMQ management HTTP API accepts request bodies larger than configured max_http_body_size

RabbitMQ: Stored XSS via TLS peer-certificate DN in stream-management UI

RabbitMQ Web Management Plugin DoS via heap overflow

RabbitMQ: Web-STOMP unbounded pre-auth accumulation

RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS

Predictable credential obfuscation seed value used in rabbitmq-server

RabbitMQ: Stream-protocol frame length never validated against frame_max

RabbitMQ: Stored XSS via TLS peer-certificate DN in management UI

RabbitMQ: Stream Management Super-Stream Binding Keys Allocation Allows Low-Privilege Node Denial of Service

RabbitMQ: Atom-table exhaustion via reply-to queue name decoding

RabbitMQ: Consecutive topic wildcards cause combinatorial routing work

RabbitMQ: LDAP DN injection via unescaped substitution

RabbitMQ: Web MQTT with PROXY Protocol enabled: a loopback-only user permission bypass

RabbitMQ: AMQP 0-9-1 body assembly never validates accumulated size

RabbitMQ: Monitoring-tag user can DELETE shovels

RabbitMQ: Incomplete fix for CVE-2026-44838: `escape_regex_char/1` does not escape `-`, leaving room for an MQTT topic permission bypass

RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message access

RabbitMQ: Stored XSS in RabbitMQ management UI

RabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass

RabbitMQ: Admin-only atom exhaustion: atomize_keys on vhost metadata

RabbitMQ: Admin-only atom exhaustion: PUT /api/users tags list

RabbitMQ: Atom exhaustion: to_atom on runtime-parameter component