CVE-2025-30219: RabbitMQ has XSS Vulnerability in an Error Message in Management UI
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: azl3 rabbitmq-server 3.13.7-2 on Azure Linux 3.0 3.13.7-2; cbl2 rabbitmq-server 3.11.24-3 on CBL Mariner 2.0 3.11.24-3; cbl2 rabbitmq-server 3.11.24-3 on CBL-Mariner 2.0 3.11.24-3.
Low priority for now. Upgrade to azl3 rabbitmq-server 3.13.7-2 on Azure Linux 3.0 3.13.7-2; cbl2 rabbitmq-server 3.11.24-3 on CBL Mariner 2.0 3.11.24-3; cbl2 rabbitmq-server 3.11.24-3 on CBL-Mariner 2.0 3.11.24-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 25, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-79
Report tools
Action score
24
Monitor
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Limit the impact of XSS
This is a cross-site scripting (XSS) vulnerability. A well-configured Content-Security-Policy doesn't fix it, but greatly reduces its impact. Check your site's CSP and other security headers for free.
Check security headersVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
rabbitmq rabbitmq-server
- < 4.0.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rabbitmq-server | from 0 | — |
| Debian:13 | rabbitmq-server | before 4.0.5-1 | 4.0.5-1 |
| openSUSE:Leap 15.6 | rabbitmq-server | before 3.8.11-150300.3.19.1 | 3.8.11-150300.3.19.1 |
| openSUSE:Leap 15.6 | rabbitmq-server313 | before 3.13.1-150600.13.8.1 | 3.13.1-150600.13.8.1 |
| openSUSE:Leap 16.0 | rabbitmq-server | before 4.1.5-160000.1.1 | 4.1.5-160000.1.1 |
| openSUSE:Tumbleweed | rabbitmq-server | before 3.13.7-4.1 | 3.13.7-4.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | rabbitmq-server | before 3.8.11-150300.3.19.1 | 3.8.11-150300.3.19.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP7 | rabbitmq-server313 | before 3.13.1-150600.13.8.1 | 3.13.1-150600.13.8.1 |
| SUSE:Linux Enterprise Server 16.0 | rabbitmq-server | before 4.1.5-160000.1.1 | 4.1.5-160000.1.1 |
Same product
rabbitmq: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-51988HTTP API's queue deletion endpoint does not verify that the user has a required permission26Monitor
- CVE-2026-67414RabbitMQ AMQP 1.0 parser: amplification memory-exhaustion DoS via zero-width array aggregation24Monitor
- CVE-2026-67418RabbitMQ MQTT 5: inapplicable PUBLISH property disconnects matching subscribers21Monitor
Published before and after this one in the same product
- Later →CVE-2026-67416Oct 14, 2026 · RabbitMQ: AMQP 1.0 symbolic body descriptor prefix collisions bypass validation21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 rabbitmq-server 3.13.7-2 on Azure Linux 3.0 | 3.13.7-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 rabbitmq-server 3.11.24-3 on CBL Mariner 2.0 | 3.11.24-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 rabbitmq-server 3.11.24-3 on CBL-Mariner 2.0 | 3.11.24-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:rabbitmq-server | 4.0.5-1 · Debian:13 | Package registry (OSV) |
| opensuse:rabbitmq-server | 3.8.11-150300.3.19.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:rabbitmq-server313 | 3.13.1-150600.13.8.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:rabbitmq-server | 3.8.11-150300.3.19.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP7 | Package registry (OSV) |
| suse:rabbitmq-server313 | 3.13.1-150600.13.8.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- low · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:L
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.