Servers and applications
CVE-2026-44839
Unsanitized vhost names allow for XSS in management UI
- Severity
- Medium 5.6
- Published
- 6 May 2026
- Last changed
- 17 Nov 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.13.10, 4.0.13, 4.1.2
- Exploit chance
- 0.2% in the next 30 daysHigher than 8% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Cross-site scripting (CWE-80)
- Attack
- Over the network · Only under certain conditions · Needs an administrator account · Needs someone to click or open something
- Attacker can
- Read data
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-fh5r-jpm3-fjwp
- Sources
- NVD, Project advisories (GitHub)
Description
Unsanitized virtual host names allow for XSS in the the management UI pages that list virtual hosts if the attacker manages to find a way to force a virtual host to restart.
The relevant blocks were introduced in https://github.com/rabbitmq/rabbitmq-server/commit/7f54319279d1ece161ae0b4cdc6f0e58a4045eb5. In vhost.ejs and vhosts.ejs the forms to restart a dead vhost include a hidden input with the vhost name without using the fmt_string sanitizer. Wrapping these values in fmt_string fixes this issue without affecting the form's functionality.
Since vhost names are not limited in length (to my knowledge), the XSS script can be arbitrarily long. It requires the ability to create vhosts as well as a means to kill them somehow, and for the attack to affect unsuspecting users they need to visit the vhost page of the malicious vhost.
Affected software
| Software | Affected versions |
|---|---|
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server |
|
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server |
|
About RabbitMQ
open source message broker, sometimes referred to as "Rabbit"
- Docker Hub pulls
- 3,918,841,187Docker Hub, 15 Nov 2026
- GitHub stars
- 13,973GitHub, 15 Nov 2026
- Forks
- 4,032GitHub, 15 Nov 2026
- Latest release
- v4.4.0GitHub, 15 Nov 2026
- Released
- 19 Oct 2026GitHub
- Developer
- Jean-Sébastien PédronWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- ErlangWikidata
- First published on GitHub
- 20 Sept 2010GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.4 | 4.4.0 | Until 31 Jul 2027 |
| 4.3 | 4.3.7 | Until 31 Jan 2027 |
| 4.2 | 4.2.9 | Ended 31 Jul 2026 |
| 4.1 | 4.1.8 | Ended 30 Jan 2026 |
| 4.0 | 4.0.9 | Ended 30 Apr 2025 |
| 3.13 | 3.13.7 | Ended 30 Sept 2024 |
From endoflife.date.
Vulnerabilities in RabbitMQ
- In our list
- 107
- Published in the last 12 months
- 89
- Critical, last 12 months
- 4
- High, last 12 months
- 22
- Known exploited
- 0
- GHSA-3wxh-g236-vm46LDAP authentication failures allow unauthenticated log amplificationHigh 8.2 25 Oct 2026
- GHSA-g73v-gcjq-2g4hAMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumersMedium 6.3 25 Oct 2026
- GHSA-6wvj-vwrc-wcrmHTML injection in management UI OAuth login warningMedium 5.7 25 Oct 2026
- GHSA-mhh3-4wv2-rrj7SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` outputMedium 5.7 25 Oct 2026
- GHSA-9h6g-46wc-m2f5Memory DoS via incomplete AMQP 0-9-1 messagesHigh 7.1 25 Oct 2026
- GHSA-j6hc-926v-qwq2RabbitMQ STOMP consumers retain OAuth queue access after JWT expirationMedium 4.9 18 Sept 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-44839
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-44839
- GitHub Advisory Database https://github.com/advisories/GHSA-fh5r-jpm3-fjwp
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-fh5r-jpm3-fjwp