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 trusted PROXY-protocol path and the backend listener is loopback-bound because the loopback check uses the listener-side socket address instead of the real client source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-130059 advisory.

    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 trusted PROXY-protocol path and the backend listener is     loopback-bound because the loopback check uses the listener-side socket address instead of the real client     source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES16 / SLES_SAP16 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:23869-1 advisory.

    - 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).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote openSUSE 16 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21903-1 advisory.

    - 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).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of RabbitMQ installed on the remote host is affected by multiple vulnerabilities:

  - 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 trusted PROXY-protocol path and the backend listener is     loopback-bound because the loopback check uses the listener-side socket address instead of the real client source.
    (CVE-2026-57216)

  - The obsolete GET /api/auth endpoint can disclose the OAuth 2 client secret on RabbitMQ installations configured     with management.oauth_client_secret, exposing credentials to unauthenticated callers when the management plugin     and that OAuth configuration are enabled. (CVE-2026-57219)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 trusted PROXY-protocol path and the backend listener is     loopback-bound because the loopback check uses the listener-side socket address instead of the real client     source. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6. (CVE-2026-57216)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
365801	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: rabbitmq-server (UTSA-2026-130059)	Nessus	Unity Linux Local Security Checks	Local	critical
350832	SUSE SLES16: erlang-rabbitmq-client / rabbitmq-server / etc (SUSE-SU-2026:23869-1)	Nessus	SuSE Local Security Checks	Local	high
350157	openSUSE 16: erlang-rabbitmq-client / rabbitmq-server / etc (openSUSE-SU-2026:21903-1)	Nessus	SuSE Local Security Checks	Local	high
327581	RabbitMQ 3.13.x < 3.13.15 / 4.0.x < 4.0.20 / 4.1.x < 4.1.11 / 4.2.x < 4.2.6 Multiple Vulnerabilities	Nessus	Misc.	Local	high
326538	Linux Distros Unpatched Vulnerability : CVE-2026-57216	Nessus	Misc.	Local	critical

Detections

Analytics

CVE-2026-57216

critical

Tenable Plugins

critical

high

high

high

critical