Summary
This update for rabbitmq-server fixes the following issues:
- CVE-2026-44839: XSS in management UI due to unsanitized vhost names (bsc#1266465).
- CVE-2026-57212: The rabbitmq_management HTTP API accepts oversized valid JSON bodies on with_decode and direct_request
paths (bsc#1271318).
- CVE-2026-57213: stored XSS in RabbitMQ federation management plugin via unsanitized consumer_tag rendering
(bsc#1271336).
- CVE-2026-57214: stored XSS in RabbitMQ management UI (bsc#1271337).
- CVE-2026-57215: direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent
phantom (bsc#1271338).
- CVE-2026-57216: stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address
loopback checks (bsc#1271339).
- CVE-2026-57217: topic authorization can lead to cross-tenant routing-key bypass (bsc#1271340).
- CVE-2026-57218: consumer persistence can lead to post-revocation message disclosure in OAuth2 (bsc#1271343).
- CVE-2026-57219: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less
common OAuth 2 configurations (bsc#1271344).
- CVE-2026-57220: stream listener does not enforce configured frame-size limit during authentication, permitting
unauth'd mem-exhaust DoS (bsc#1271345).
- CVE-2026-57221: passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to
unprivileged users (bsc#1271346).
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| SUSE · SLES 16.0 Linux Enterprise Server 16.0 | rabbitmq-server | 4.1.5-160000.2.1 |
| SUSE · SLES for SAP 16.0 Linux Enterprise Server for SAP applications 16.0 | rabbitmq-server | 4.1.5-160000.2.1 |
Vulnerabilities 11
-
High 8.7CVE-2026-57219 Scanner template
RabbitMQ: Unauthenticated disclosure of OAuth client credentials via an HTTP API endpoint with certain less common OAuth 2 configurations
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, the obsolete GET /api/auth endpoint can disclose the OAuth 2 client secret on RabbitMQ installations configured with management.oauth_client_secret, exposing credential…
-
High 7.5
RabbitMQ: Stream listener does not enforce configured frame-size limit during authentication, permitting unauth'd mem-exhaust DoS
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, the RabbitMQ stream listener does not enforce the configured stream frame-size limit while assembling frames during authentication and before Tune negotiation, allowing an unauthenticated remote cl…
-
High 7.1
RabbitMQ management HTTP API accepts request bodies larger than configured max_http_body_size
RabbitMQ is a messaging and streaming broker. Prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the rabbitmq_management HTTP API accepts oversized valid JSON bodies on with_decode and direct_request paths because read_complete_body checks the accumulated size befo…
-
High 7.1
RabbitMQ: Stored XSS in RabbitMQ management UI
RabbitMQ is a messaging and streaming broker. Prior to 4.2.5, the RabbitMQ management UI renders the x-internal-purpose queue or exchange argument into an HTML title attribute without proper escaping on the Queues and Exchanges pages, allowing a user with per…
-
High 7.0
RabbitMQ: Direct-reply-to binding persistence can lead to unauthorized reply-channel injection and persistent phantom
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ allows foreign bindings to amq.rabbitmq.reply-to destinations because volatile direct-reply-to queues can be accepted at bind and route time but are missing fr…
-
High 7.0
RabbitMQ: Topic authorization can lead to cross-tenant routing-key bypass
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.21, 4.1.11, and 4.2.6, RabbitMQ topic authorization can allow restricted topic writes and binds during metadata-store failures because topic-permission lookup errors from Khepri can collapse …
-
Medium 6.8
RabbitMQ: AMQP 1.0, AMQP 0-9-1, Stream Protocol loopback enforcement can lead to remote guest sessions due to listener-address loopback checks
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, AMQP 0-9-1, AMQP 1.0, and Stream Protocol authentication can allow a loopback-restricted user such as guest to connect remotely when traffic is accepted through a trust…
-
Medium 5.7
RabbitMQ: Stored XSS federation management plugin via unsanitized consumer_tag rendering
RabbitMQ is a messaging and streaming broker. Prior to 3.13.14, 4.0.19, 4.1.10, and 4.2.5, the rabbitmq_federation_management plugin renders the consumer_tag field on the Federation Status page without HTML escaping, allowing a user who can configure a federa…
-
Medium 5.6
RabbitMQ: Unsanitized vhost names allow for XSS in management UI
RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.
-
Medium 5.3
RabbitMQ: Passive queue/exchange declaration bypasses authorization checks, leaking queue metadata to unprivileged users
RabbitMQ is a messaging and streaming broker. Prior to 3.13.15, 4.0.20, 4.1.11, and 4.2.6, RabbitMQ does not perform authorization checks on passive queue.declare and exchange.declare AMQP 0-9-1 operations, allowing any authenticated user who can connect to a…
-
Medium 4.9
RabbitMQ: AMQP 0-9-1 in combination with OAuth 2: consumer persistence can lead to post-revocation message disclosure
RabbitMQ is a messaging and streaming broker. Prior to 4.2.6, RabbitMQ AMQP 0-9-1 allows an existing consumer to keep receiving messages after OAuth token expiry or connection.update_secret refresh to reduced scopes because existing consumers are not canceled…
References
-
report
https://bugzilla.suse.com/1266465
-
report
https://bugzilla.suse.com/1271318
-
report
https://bugzilla.suse.com/1271336
-
report
https://bugzilla.suse.com/1271337
-
report
https://bugzilla.suse.com/1271338
-
report
https://bugzilla.suse.com/1271339
-
report
https://bugzilla.suse.com/1271340
-
report
https://bugzilla.suse.com/1271343
-
report
https://bugzilla.suse.com/1271344
-
report
https://bugzilla.suse.com/1271345
-
report
https://bugzilla.suse.com/1271346
-
report
https://bugzilla.suse.com/1279938
-
web
https://www.suse.com/security/cve/CVE-2026-44839
-
web
https://www.suse.com/security/cve/CVE-2026-57212
-
web
https://www.suse.com/security/cve/CVE-2026-57213
-
web
https://www.suse.com/security/cve/CVE-2026-57214
-
web
https://www.suse.com/security/cve/CVE-2026-57215
-
web
https://www.suse.com/security/cve/CVE-2026-57216
-
web
https://www.suse.com/security/cve/CVE-2026-57217
-
web
https://www.suse.com/security/cve/CVE-2026-57218
-
web
https://www.suse.com/security/cve/CVE-2026-57219
-
web
https://www.suse.com/security/cve/CVE-2026-57220
-
web
https://www.suse.com/security/cve/CVE-2026-57221