First published: Tue Mar 25 2025(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
<4.0.3 | ||
<4.0.3<3.13.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2025-30219 has a high severity level due to its potential for arbitrary JavaScript code execution.
To resolve CVE-2025-30219, upgrade your RabbitMQ or Tanzu RabbitMQ installation to version 4.0.3 or higher.
CVE-2025-30219 affects RabbitMQ versions prior to 4.0.3 and Tanzu RabbitMQ versions prior to 3.13.8 and 4.0.3.
CVE-2025-30219 allows attackers to modify virtual host names on disk and potentially execute arbitrary JavaScript code.
CVE-2025-30219 is considered a remote vulnerability as it can be exploited over the network.