# CVE-2026-44839: RabbitMQ: Unsanitized vhost names allow for XSS in management UI

> Attackers can inject malicious scripts via unsanitized vhost names in the RabbitMQ management UI, potentially compromising user sessions.

- **Severity:** Medium 5.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** AZL-89289, BIT-rabbitmq-2026-44839, DEBIAN-CVE-2026-44839, GHSA-fh5r-jpm3-fjwp, UBUNTU-CVE-2026-44839

## What is CVE-2026-44839?

CVE-2026-44839 is a medium-severity cross-site scripting vulnerability in Broadcom Rabbitmq Server, published on 27 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

## Which versions are affected by CVE-2026-44839?

1 open source package ship an affected version, including rabbitmq. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rabbitmq` | Bitnami | From 3.7.0 | 4.0.13, 4.1.2 |

Products: Broadcom Rabbitmq Server.

## How do I fix CVE-2026-44839?

Upgrade rabbitmq to a fixed version for your release line: 4.0.13 or 4.1.2.

## Is CVE-2026-44839 being exploited?

There is no known exploitation of CVE-2026-44839 in the wild and no public exploit code.

## Other vulnerabilities in Broadcom Rabbitmq Server

- [CVE-2016-9877](https://insights.sbomify.com/CVE-2016-9877/): Auth bypass in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6; RabbitMQ for PCF 1.5.x before 1.5.20, 1.6.x before 1.6.12 and 1.7.x before 1.7.7 (critical 9.8)
- [CVE-2026-67404](https://insights.sbomify.com/CVE-2026-67404/): RabbitMQ: OAuth2 silent verify_none fallback for JWKS fetch (critical 9.2)
- [CVE-2026-67231](https://insights.sbomify.com/CVE-2026-67231/): RabbitMQ: Trust-store whitelist by Issuer+Serial only (critical 9.1)
- [CVE-2026-57219](https://insights.sbomify.com/CVE-2026-57219/): Information disclosure in rabbitmq-server (high 8.7)
- [CVE-2026-67236](https://insights.sbomify.com/CVE-2026-67236/): RabbitMQ: Plaintext username:password stored in an insecure cookie after successful POST /login (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44839 and fix it if it is affected.

What it is: CVE-2026-44839 is a medium-severity cross-site scripting vulnerability in Broadcom Rabbitmq Server, published on 27 May 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44839 in the wild and no public exploit code.

Affected packages and fixed versions:
- rabbitmq (Bitnami): affected from 3.7.0; fixed in 4.0.13, 4.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44839/ (Markdown: https://insights.sbomify.com/CVE-2026-44839/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44839
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44839
- OSV: https://osv.dev/vulnerability/CVE-2026-44839

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44839/
Summaries are generated and may contain mistakes; the official description above is the record.