The remote Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS / 24.10 host has a package installed that is affected by a vulnerability as referenced in the USN-7399-1 advisory.

    It was discovered that RabbitMQ Server's management UI did not sanitize certain input. An attacker could     possibly use this issue to inject code by performing a cross-site scripting (XSS) attack.

Tenable has extracted the preceding description block directly from the Ubuntu 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 SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:1466-1 advisory.

    - CVE-2025-30219: Fixed XSS in an error message in Management UI (bsc#1240071)

    Other fixes:
    - Disable parallel make, this causes build failures

Tenable has extracted the preceding description block directly from the SUSE 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 SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:1548-1 advisory.

    - CVE-2025-30219: incorrectly escaped virtual hostname present in error message could lead to XSS attack.
    (bsc#1240071)

    Non-security fixes:

    - Require rabbitmq-server313-plugins rather then rabbitmq-server-plugins. (bsc#1231656, bsc#1234763)

Tenable has extracted the preceding description block directly from the SUSE 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 version of rabbitmq-server installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-30219 advisory.

  - RabbitMQ is a messaging and streaming broker. Versions prior to 4.0.3 are vulnerable to a sophisticated     attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file     modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users.
    When a virtual host on a RabbitMQ node fails to start, recent versions will display an error message (a     notification) in the management UI. The error message includes virtual host name, which was not escaped     prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An attack that both makes a virtual     host fail to start and creates a new virtual host name with an XSS code snippet or changes the name of an     existing virtual host on disk could trigger arbitrary JavaScript code execution in the management UI (the     user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ `4.0.3` and `3.13.8` patch the issue.
    (CVE-2025-30219)

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

RabbitMQ is a messaging and streaming broker. Versions prior to 4.0.3 are vulnerable to a sophisticated attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users. When a virtual host on a RabbitMQ node fails to start, recent versions will display an error message (a notification) in the management UI. The error message includes virtual host name, which was not escaped prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An attack that both makes a virtual host fail to start and creates a new virtual host name with an XSS code snippet or changes the name of an existing virtual host on disk could trigger arbitrary JavaScript code execution in the management UI (the user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ `4.0.3` and `3.13.8` patch the issue.

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. Versions prior to 4.0.3 are vulnerable to a sophisticated     attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file     modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users.
    When a virtual host on a RabbitMQ node fails to start, recent versions will display an error message (a     notification) in the management UI. The error message includes virtual host name, which was not escaped     prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An attack that both makes a virtual     host fail to start and creates a new virtual host name with an XSS code snippet or changes the name of an     existing virtual host on disk could trigger arbitrary JavaScript code execution in the management UI (the     user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ `4.0.3` and `3.13.8` patch the issue.
    (CVE-2025-30219)

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

An update of the rabbitmq package has been released.

The remote openSUSE 16 host has packages installed that are affected by a vulnerability as referenced in the openSUSE- SU-2026:20082-1 advisory.

    Changes in rabbitmq-server:

    Update to 4.1.5:

    * Highlights

      - Khepri, an alternative schema data store developed to replace Mnesia,         has matured and is now fully supported (it previously was an experimental feature)
      - AMQP 1.0 is now a core protocol that is always enabled. Its plugin is now a no-op that only exists to     simplify upgrades.
      - The AMQP 1.0 implementation is now significantly more efficient: its peak throughput is more than     double than that of 3.13.x         on some workloads
      - Efficient sub-linear quorum queue recovery on node startup using checkpoints
      - Quorum queues now support priorities (but not exactly the same way as classic queues)
      - AMQP 1.0 clients now can manage topologies similarly to how AMQP 0-9-1 clients do it
      - The AMQP 1.0 convention (address format) used for interacting with with AMQP 0-9-1 entities is now     easier to reason about
      - Mirroring (replication) of classic queues was removed after several years of deprecation. For     replicated messaging data types,         use quorum queues and/or streams. Non-replicated classic queues remain and their development continues
      - Classic queue storage efficiency improvements, in particular recovery time and storage of multi-MiB     messages
      - Nodes with multiple enabled plugins and little on disk data to recover now start up to 20-30% faster
      - New exchange type: Local Random Exchange
      - Quorum queue log reads are now offloaded to channels (sessions, connections).
      - Initial Support for AMQP 1.0 Filter Expressions
      - Feature Flags Quality of Life Improvements
      - rabbitmqadmin v2

    * Breaking Changes

      - Before a client connection can negotiate a maximum frame size (frame_max), it must authenticate         successfully. Before the authenticated phase, a special lower frame_max value         is used.
      - With this release, the value was increased from the original 4096 bytes to 8192         to accommodate larger JWT tokens.
      - amqplib is a popular client library that has been using         a low frame_max default of 4096. Its users must upgrade to a compatible version         (starting with 0.10.7) or explicitly use a higher frame_max.
        amqplib versions older than 0.10.7 will not be able to connect to         RabbitMQ 4.1.0 and later versions due to the initial AMQP 0-9-1 maximum frame size         increase covered above.
      - The default MQTT Maximum Packet Size changed from 256 MiB to 16 MiB.
      - The following rabbitmq.conf settings are unsupported:

        - cluster_formation.etcd.ssl_options.fail_if_no_peer_cert
        - cluster_formation.etcd.ssl_options.dh
        - cluster_formation.etcd.ssl_options.dhfile

      - Classic Queues is Now a Non-Replicated Queue Type
      - Quorum Queues Now Have a Default Redelivery Limit
      - Up to RabbitMQ 3.13, when an AMQP 0.9.1 client (re-)published a message to RabbitMQ, RabbitMQ     interpreted the
      - AMQP 0.9.1 x-death header in the published message's basic_message.content.properties.headers field.
      - RabbitMQ 4.x will not interpret this x-death header anymore when clients (re-)publish a message.
      - CQv1 Storage Implementation was Removed
      - Settings cluster_formation.randomized_startup_delay_range.* were Removed
      - Several Disk I/O-Related Metrics were Removed
      - Default Maximum Message Size Reduced to 16 MiB
      - RabbitMQ 3.13 rabbitmq.conf setting rabbitmq_amqp1_0.default_vhost is unsupported in RabbitMQ 4.0.
      - RabbitMQ 3.13 rabbitmq.conf settings mqtt.default_user, mqtt.default_password,         and amqp1_0.default_user are unsupported in RabbitMQ 4.0.
      - Starting with Erlang 26, client side TLS peer certificate chain verification settings are enabled by     default in most contexts:
        from federation links to shovels to TLS-enabled LDAP client connections.
      - RabbitMQ Shovels will be able connect to a RabbitMQ 4.0 node via AMQP 1.0 only when the Shovel runs on     a RabbitMQ node >= 3.13.7.

        * See https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.0.1
        * and https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0 for more info

    - Restore SLES logrotate file, (bsc#1246091)

Tenable has extracted the preceding description block directly from the SUSE 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 SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:01466-1 advisory.

    - CVE-2025-30219: Fixed XSS in an error message in Management UI (bsc#1240071)

    Other fixes:
    - Disable parallel make, this causes build failures

Tenable has extracted the preceding description block directly from the SUSE 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 SLES15 / SLES_SAP15 host has packages installed that are affected by a vulnerability as referenced in the SUSE-SU-2025:01548-1 advisory.

    - CVE-2025-30219: incorrectly escaped virtual hostname present in error message could lead to XSS attack.
    (bsc#1240071)

    Non-security fixes:

    - Require rabbitmq-server313-plugins rather then rabbitmq-server-plugins. (bsc#1231656, bsc#1234763)

Tenable has extracted the preceding description block directly from the SUSE 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 version of rabbitmq-server installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2025-30219 advisory.

  - RabbitMQ is a messaging and streaming broker. Versions prior to 4.0.3 are vulnerable to a sophisticated     attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file     modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users.
    When a virtual host on a RabbitMQ node fails to start, recent versions will display an error message (a     notification) in the management UI. The error message includes virtual host name, which was not escaped     prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An attack that both makes a virtual     host fail to start and creates a new virtual host name with an XSS code snippet or changes the name of an     existing virtual host on disk could trigger arbitrary JavaScript code execution in the management UI (the     user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ `4.0.3` and `3.13.8` patch the issue.
    (CVE-2025-30219)

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

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the TSSA-2025:0265 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2025-30219:
    RabbitMQ is a messaging and streaming broker. Versions prior to 4.0.3 are vulnerable to a sophisticated     attack that could modify virtual host name on disk and then make it unrecoverable (with other on disk file     modifications) can lead to arbitrary JavaScript code execution in the browsers of management UI users.
    When a virtual host on a RabbitMQ node fails to start, recent versions     will display an error message (a notification) in the management UI. The error message includes virtual     host name, which was not escaped prior to open source RabbitMQ 4.0.3 and Tanzu RabbitMQ 4.0.3, 3.13.8. An     attack that both makes a virtual host fail to start and creates a new virtual host name with an XSS code     snippet or changes the name of an existing virtual host on disk could trigger arbitrary JavaScript code     execution in the management UI (the user's browser). Open source RabbitMQ `4.0.3` and Tanzu RabbitMQ     `4.0.3` and `3.13.8` patch the issue.

Tenable has extracted the preceding description block directly from the Tencent 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.

ID	Name	Product	Family	Published	Updated	Severity
233577	Ubuntu 20.04 LTS / 22.04 LTS / 24.04 LTS / 24.10 : RabbitMQ Server vulnerability (USN-7399-1)	Nessus	Ubuntu Local Security Checks	3/31/2025	1/21/2026	medium
235633	SUSE SLES15 / openSUSE 15 Security Update : rabbitmq-server (SUSE-SU-2025:1466-1)	Nessus	SuSE Local Security Checks	5/9/2025	5/9/2025	medium
236795	SUSE SLES15 / openSUSE 15 Security Update : rabbitmq-server313 (SUSE-SU-2025:1548-1)	Nessus	SuSE Local Security Checks	5/15/2025	5/15/2025	medium
234064	CBL Mariner 2.0 Security Update: rabbitmq-server (CVE-2025-30219)	Nessus	MarinerOS Local Security Checks	4/9/2025	1/21/2026	medium
235082	RabbitMQ < 3.13.8 / 4.0.x < 4.0.3 XSS (GHSA-g58g-82mw-9m3p)	Nessus	Misc.	5/2/2025	1/21/2026	medium
259602	Linux Distros Unpatched Vulnerability : CVE-2025-30219	Nessus	Misc.	8/30/2025	8/30/2025	medium
271188	Photon OS 5.0: Rabbitmq PHSA-2025-5.0-0646	Nessus	PhotonOS Local Security Checks	10/22/2025	10/22/2025	medium
296555	openSUSE 16 Security Update : rabbitmq-server (openSUSE-SU-2026:20082-1)	Nessus	SuSE Local Security Checks	1/26/2026	1/26/2026	medium
240774	SUSE SLES15 Security Update : rabbitmq-server (SUSE-SU-2025:01466-1)	Nessus	SuSE Local Security Checks	6/27/2025	6/27/2025	medium
240830	SUSE SLES15 Security Update : rabbitmq-server313 (SUSE-SU-2025:01548-1)	Nessus	SuSE Local Security Checks	6/27/2025	6/27/2025	medium
276938	Photon OS 4.0: Rabbitmq PHSA-2025-4.0-0915	Nessus	PhotonOS Local Security Checks	12/1/2025	12/1/2025	medium
234532	Azure Linux 3.0 Security Update: rabbitmq-server (CVE-2025-30219)	Nessus	Azure Linux Local Security Checks	4/17/2025	1/21/2026	medium
239399	TencentOS Server 4: rabbitmq-server (TSSA-2025:0265)	Nessus	Tencent Local Security Checks	6/16/2025	12/4/2025	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium