CVE-2026-44839
Analyzed Analyzed - Analysis Complete
Remote Code Execution in RabbitMQ

Publication date: 2026-05-27

Last updated on: 2026-06-04

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-06-04
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
broadcom rabbitmq_server From 3.7.0 (inc) to 4.0.13 (exc)
broadcom rabbitmq_server From 4.1.0 (inc) to 4.1.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-80 The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

CVE-2026-44839 is a Cross-Site Scripting (XSS) vulnerability in RabbitMQ's management UI caused by unsanitized virtual host names. This type of vulnerability can potentially lead to unauthorized script execution in the context of the affected application.

While the provided information does not explicitly mention compliance with standards such as GDPR or HIPAA, XSS vulnerabilities can pose risks to data confidentiality and integrity, which are critical aspects of these regulations.

Organizations using vulnerable versions of RabbitMQ might face challenges in maintaining compliance if the vulnerability is exploited to access or manipulate sensitive data, as required protections under GDPR, HIPAA, and similar standards could be compromised.

The vulnerability has been patched in RabbitMQ versions 4.1.2 and 4.0.13, so applying these updates is important to mitigate compliance risks.

Executive Summary

CVE-2026-44839 is a vulnerability in RabbitMQ's management UI that allows Cross-Site Scripting (XSS) attacks. It occurs because virtual host (vhost) names are not properly sanitized in the UI, specifically in the vhost.ejs and vhosts.ejs files. An attacker who can create and kill vhosts can inject malicious scripts into the vhost names. When other users visit the affected vhost pages, these scripts can execute, potentially compromising their session or data.

The vulnerability is related to a feature that allows administrators to restart crashed vhosts via a new API endpoint and UI buttons. The lack of input sanitization in this context enables the XSS attack.

Impact Analysis

This vulnerability can impact you by allowing attackers to execute arbitrary scripts in the context of your RabbitMQ management UI. This can lead to session hijacking, unauthorized actions performed on behalf of legitimate users, or exposure of sensitive information.

To exploit this vulnerability, an attacker needs the ability to create and kill virtual hosts and rely on user interaction to trigger the malicious script execution.

The severity is rated as Moderate with a CVSS score of 5.6, indicating a significant but not critical risk.

Detection Guidance

This vulnerability involves Cross-Site Scripting (XSS) in the RabbitMQ management UI caused by unsanitized virtual host (vhost) names. Detection involves checking if your RabbitMQ server is running a vulnerable version (greater than 3.7.0 but before 4.1.2 or 4.0.13) and if the management UI allows creation and restart of vhosts with unsanitized names.

You can detect potentially vulnerable instances by verifying the RabbitMQ version using the following command:

  • rabbitmqctl status | grep '{rabbit,"RabbitMQ"'

Additionally, you can inspect the management UI for the presence of the new API endpoint `/vhosts/:vhost/start/:node` which is related to the vulnerability.

To check for suspicious or malicious vhost names that might contain script tags, you can list all vhosts with:

  • rabbitmqctl list_vhosts

Look for any vhost names containing suspicious characters or script tags that could indicate an attempted XSS exploit.

Mitigation Strategies

The primary mitigation step is to upgrade RabbitMQ to a fixed version, specifically version 4.1.2 or 4.0.13 or later, where the vulnerability has been patched.

Until you can upgrade, restrict the ability to create and restart virtual hosts to trusted administrators only, as the exploit requires the ability to create and kill vhosts.

Additionally, monitor and sanitize vhost names to prevent injection of malicious scripts.

Consider disabling or limiting access to the management UI if it is not necessary, to reduce exposure.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44839. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart